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
We want to upgrade our build servers to run our typemock tests, but I'm having a bit of trouble getting it configured correctly and finding the correct information regarding this. Our setup is a TFS2010, with 20+ projects each running from TypeMock 5.x to 6.2.2. All build definitions are msbuild based, since we are waiting to get TypeMock working with our workflow template (that besides the scope of this post). Now, I have installed Isolator 7.0 on the build servers, but I cannot seem to figure our how to make typemock work. Various questions I have.

1. Since TypeMock is installed on the build servers, I would expect that I didn't have to add any additional assemblies to source control and reference them. But it doesn't seem that the assemblies are in the GAC - Why not.
2. Since TypeMock is installed, I would expect that I didn't need to call the register (or publish for that matter) target in msbuild with licensing information - Is this correct?
3. I need to support various version of TypeMock from 5.x to 6.2.2, but have installed 7.0 on the build server. Do I need any version specific assemblies in source control pr. project and which?
4. What is the recommended way of using typemock with msbuild team build def's, when we have 7.0 on the server and 6.2.2 on the clients - what to install and where, assemblies in source control or not etc.

I've read all the documentation on this site, but still can't get this configured correctly. Regarding q3, I've now included typemock.dll, arrangeactassert.dll and configuration.dll to source control, however mstest failes without further description (TF270015: 'MSTest.exe' returned an unexpected exit code. Expected '0'; actual '-1')
Any help is greatly appreciated!
asked by jnus (18.9k points)

3 Answers

0 votes
Hi,

If you installed typemock on the build server, then you do not need to run the register/publish targets.

As of v7 the GAC should have only the typemock.interceptors.dll

Isolator v7 supports side by side versions of isolator, so it should make it easier to support different versions:

Each project that needs a different typemock version should reference the appropriate one.

If you continue having troubles with this issue then we should probably set up an online session. Please send an email with your contact details to support@typemock.com
answered by yoel (1.9k points)
0 votes
Hi,

If you installed typemock on the build server, then you do not need to run the register/publish targets.

Only for projects using 7.0 or also 6 and 5? Still need to call start and stop? Can I import v7 targets for 6.x and 5.x projects?
As of v7 the GAC should have only the typemock.interceptors.dll

Isolator v7 supports side by side versions of isolator, so it should make it easier to support different versions:

Each project that needs a different typemock version should reference the appropriate one.

Hmm - seems like a contradicting statement. Say I have a c# project referencing 6.2.2 assemblies (specific version set to false), running 6.2.2 desktop version and 7.0 server version on the build server, including the 7.0 target file in my build definition. Can I run these tests on the build server, without including the 6.2.2 assemblies in source control and referencing them directly from my project?

If you continue having troubles with this issue then we should probably set up an online session. Please send an email with your contact details to support@typemock.com
answered by jnus (18.9k points)
0 votes
You don't need the register action for any version. The installed version is taking care of the "registration" part.

You still need to run the start/stop though.

If you wish to use 6.2.2 versions or 5.x (>5.3.2) thats fine, just put them in a dependency folder (add them to source control) and reference them from your test project.

But anyway, if you don't include the typemock dlls in source control, then where will you point your reference to? you can point it to the default installation directory (i.e. c:\program files\typemock\typemock.dll), but then if some developer installed isolator to a different directory you will have problems.
answered by yoel (1.9k points)
...