Hi. I'm running a series of unit tests via TMockRunner.
On one machine, a Windows Server 2003 machine that includes NCover 3.1.4 (I've linked NCover using Isolator Configuration), the TMockRunner hangs.
On another machine, a Windows XP machine, the tests run just fine. Both machines have the same versions of .NET and Isolator installed.
Additionally the Unit Tests are run via TeamCity's NUnitLauncher (
http://www.jetbrains.com/teamcity/) 4.0.1, specifying in NUnitLauncher's parameters that .NET 2.0 should be used.
Now, I've had TypeMock log and I get this:
On Windows 2003 machine, build hangs:
Logging program: C:BuildAgentpluginsdotnetPlugininJetBrains.BuildServer.NUnitLauncher.exe
Cannot read EnvName0 => The system cannot find the file specified.
Reset Location: C:PROGRA~1NCoverNC54F4~1.DLL
Adding profiler: {9721F7EB-5F92-447c-9F75-79278052B7BA}
Loaded C:PROGRA~1NCoverNC54F4~1.DLL
Adding typemock profiler
Loaded C:Program FilesTypemockIsolator.3MockWeaver.dll
Target Runtime .NET 1.1
Initialize Profiler 0, Target Runtime .NET 1.1
Initialize Profiler 1, Target Runtime .NET 1.1
On the Windows XP machine, tests run:
Logging program: C:BuildAgentpluginsdotnetPlugininJetBrains.BuildServer.NUnitLauncher.exe
Cannot read EnvName0 => The system cannot find the file specified.
Cannot read ResetCLSID => The system cannot find the file specified.
Adding typemock profiler
Loaded C:Program FilesTypemockIsolator.3MockWeaver.dll
Target Runtime .NET 2.0
Initialize Profiler 0, Target Runtime .NET 2.0
This suggests (at least to me) that for some reason on the Windows Server 2003 machine that TMockRunner.exe is trying to run under .NET 1.1, which Isolator 5.3 is not compatible with; furthermore on the Windows XP machine the same command (it's scripted, we can repeat it exactly in the different environments) runs under .NET 2.0, and doesn't hang.
I tried passing the "-target 2.0" switch to TMockRunner.exe, but this caused an unhandled exception to be thrown, in both environments.
I'd be grateful if anyone has any suggestions?
Ta,
W.
