Auto Deploying Typemock Isolator

Auto-Deployment

Creating a build server can be a daunting task. To make it easier, Typemock Isolator has a method that enables you to run Typemock Isolator tests without installing Typemock Isolator on the machine.

Deploying Typemock Isolator this way will enable less features that help you write tests, like Visual Studio integration, but is sufficient to run the tests.

How to Auto-Deploy

To auto-deploy, you must copy the following Typemock Isolator files for installation:

Where to place MockWeaver.dll and ProfileLinker.dll files:

Single platform deployment (x86 OR x64)

For the basic setup, copy the MockWeaver.DLL and ProfileLinker.DLL from the x86 or x64 folder under the Isolator installation directory. The target folder for auto-deployment should contain all the files in a single folder. This deployment is supported for backward compatibility.

Multiple platforms deployment (x86 AND x64)

Create sub-folders for x86 and x64 in the target dirctory. Copy the MockWeaver.DLL and ProfileLinker.DLL from the x86 and x64 folders under the Isolator installation directory to the sub-folders in the target direcotry.
In case of running on 32 bit machine machine the x64 files will be ignored. It is safe to use this method both on 32 and 64 bit machines.

To deploy, use the MSBuild, FinalBuilder or NAnt TypeMockRegister task.

MSBuild Example
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
 <PropertyGroup> 
 <TypeMockLocation>c:\Program Files\Typemock\Isolator\5.0</TypeMockLocation>
 </PropertyGroup> 
 <Import Project ="$(TypeMockLocation)\TypeMock.MSBuild.Tasks"/>

<Target Name="RegisterTypeMock"> <TypeMockRegister Company ="TypeMock" License="TypeMockLicense" AutoDeploy="True"/>
 </Target>

</Project>

How to Undeploy

To undeploy Typemock Isolator, you need the following files:

To undeploy, use the MSBuild or NAnt TypeMockStop task with Undeploy="true" or use TMockRunner.exe -undeploy.

 

Copyright © Typemock Ltd. 2004-2010. All Rights Reserved.