chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
I considered posting this in the Feature Requests topic, but thought I'd try it out here, first, since it's sort of an edge-case.

I'd like to see the ability for multiple versions of Typemock to be installed on a box and running side-by-side. Not necessarily all at the same time, multi-threaded style, but something similar to the VS 2008 multi-targeting feature so I could have Typemock 4.0.0 and 4.1.0 installed on the same machine and say "build this and run against 4.0.0, but build that and run against 4.1.0." Maybe have an option in the little Typemock admin panel thing that lets me choose the "active Typemock version" or something.

It would make it far easier to take an upgrade - I could install the new version on my developer box and try things out to see if it all works (so I can recommend the upgrade be taken or troubleshoot if there's anything wrong) without having to uninstall or upgrade an existing installation.

The specific use case I have in mind: the latest beta. I have to think about how I'm going to try it out...
  • Do I install on my developer machine or do I create a VM image to test this on?
  • If I create a VM image, when, exactly, do I have time to do that?
  • If I install on my developer box, I'm not building with the same tools as the rest of the group so before I commit, I really need to uninstall and reinstall the old version to make sure I didn't accidentally add a bunch of tests using features we don't have yet.
asked by tillig (6.7k points)

3 Answers

0 votes

:idea: I think that the "AutoDeploy" mechanism can be used in your case.
it should allow you to run against a typemock placed in a folder of your choosing.

I will need to check and see if its completely version independan.
answered by lior (13.2k points)
0 votes
I was thinking about something a little more robust and accessible than that. Something with UI to it so I don't have a bunch of "switch TypeMock version" scripts floating around that I have to mess with. Like, the ability to change the version from the VS add-in or the TypeMock control panel.

Even if I could use AutoDeploy, it means I have to:
  • Run the installer the first time so I can get to the binaries.
  • Copy the appropriate items out of the installed location.
  • Uninstall so future installs won't clash.
  • Set up my own folder hierarchy with the various versions of TypeMock.
  • Write the scripts to AutoDeploy.
  • Run the scripts to change versions.

Then, though, I lose some of the goodness like the tracer and the admin UI for linking other profilers, don't I? Or would I also need to create my own Start Menu icon hierarchy to point to the relevant utilities in the folder hierarchy that I had to create?

Like I said, I think something more formally supported would be helpful. Install and go, switch through a nice UI or through a programmatic interface (that the nice UI would presumably be using) so I could script it if I need to without assuming AutoDeploy.
answered by tillig (6.7k points)
0 votes

Sorry for the delayed response.

I actually think that this will be a great feature to implement. It will certainly help the adaption of new release.

When i was refering to the auto deploy. I thought of it as a temporary work around that maybe help for the meantime.

However, I did forgot to mention that. sorry :twisted:
answered by lior (13.2k points)