I also emailed this information to your support group.
We are attempting to upgrade our team to Isolator 5.1.1 from 4.2.4. Part of that upgrade includes upgrading our build server, which is running Windows Server 2003 R2 Standard x64 Service Pack 2. Instead of installing the new version, I decided to uninstall the previous release and then to update our automated build scripts (using MSBuild) to use the Auto-Deploy (<TypeMockRegister>) feature. An excerpt from my MSBuild script is included below:
<TypeMockLocation>E:TypeMockAssemblies.1</TypeMockLocation>
<Import Project ="$(TypeMockLocation)TypeMock.MSBuild.Tasks"/>
...
<TypeMockRegister Company="our company" License="our license" AutoDeploy="true" />
<TypeMockStart Target="2.0" LogLevel="9" LogPath="$(NUnitOutputPath)" />
<exec Command="$(NUnit) $(NUnitAssemblyName) /xml $(NUnitOutputPath)$(NUnitResultsFile) /exclude:DatabaseIntegrationTest"/>
<TypeMockStop />
The register task appears to run ok. However, when I execute the unit tests, many of them fail with the following exception:
TypeMock.TypeMockException : *** Typemock Isolator needs to be linked with Coverage Tool to run, to enable do one of the following: 1. link the Coverage tool through the Typemock Isolator Configuration 2. run tests via TMockRunner.exe -link 3. use TypeMockStart tasks for MSBuild or NAnt with Link For more information consult the documentation (see Code Coverage with Typemock Isolator topic)
at TypeMock.MockManager.Init(Boolean collectAllCalls)
at TypeMock.MockManager.e(Type A_0)
at TypeMock.MockManager.Mock(Type type, Constructor mockConstructors)
at TypeMock.MockManager.MockObject(Type type, Constructor mockConstructors, Object[] args)
at TypeMock.RecorderManager.CreateMockedObject(Type typeToMock, Constructor mockConstructor, StrictFlags strictFlags, Object[] args)
at TypeMock.RecorderManager.CreateMockedObject[TMockedType](Constructor mockConstructors, StrictFlags strictFlags, Object[] args)…
We are not attempting to run the NCover tool, nor is it installed on our build server. I’ve done some web searches and have seen that others have had a similar error (see below) but I haven’t been able to find a resolution.
https://www.typemock.com/community/viewtopic.php?p=3679
https://www.typemock.com/community/viewt ... 15d5686e87
Some further, possibly helpful, information is that, to get the TypeMock x64 assemblies to use for the auto-deploy option, I first installed it on the build machine, made copies of the assemblies, and then uninstalled it. After that, I created a “TypeMockAssemblies.1” folder to use as the location for the auto-deploy files and copied in the files indicated in the TypeMock documentation, first taking MockWeaver.dll and ProfileLinker.dll from the x64 folder of the install directory. When I ran the first test of this setup, it resulted in some type of error when it attempted to register MockWeaver.dll. (I can get you detailed error information, if need be.) So, since the documentation says to use the x86 version of that and the ProfileLinker assemblies, I then copied the x86 versions over the x64 versions in my “TypeMockAssemblies.1”. The registration completed and it began to execute the unit tests and that is when I encountered the “Coverage Tool” issue.
I spoke with a coworker that had encountered the same issue when first setting up TypeMock on our build server. She said that to resolve the issue she had to remove the <TypeMockStop> instruction. However, I just tried this and it did not solve the issue.
One thing I should also note is that the assembly containing the unit tests was compiled with the 4.2.4 release of Isolator. I realize this will be a problem but I expect to get a different error message for that reason. I will resolve that issue shortly.
