TypeMock 7 and Build Server Configuration

Question

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 e.g. 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 the TypeMock site, but still can't get this configured correctly.

Answer 1

1. The test projects reference a specific version of Isolator (5.x, 6.2.2). Since the assemblies are required during the build the assemblies must be located in the place where the build can find them. Since Isolator 7.0 is installed the only assemblies that can be found are 7.0 version. Isolator 7.0 can execute older versions but the original assemblies must be accessible. Therefor, the original assemblies need to be in the source control.

2. If Isolator is installed there's not need to call register actions, only start & stop. You need to be sure that the license was set once on the server using the Isolator Configuration utility.

3. In general, you'll need to place all the assemblies required for auto-deploy. In most cases, having Typemock.dll, Typemock.ArrangeActAssert.dll and Configuration.dll.

4. The client can have installed any version > 5.3.4, the server should have V7.0 installed. In the source control the assemblies from (3) should be stored.

Disclaimer - I work at Typemock