Hello,
We have downloaded a 3.6 upgrade and bought a new license for a build server. Then our problems began. Right now I can use TypeMock on my machine, but if I try to run tests (using TestDriven.NET) on a build server, then as long as TypeMock is enabled nothing happens: after a long waiting time VS prints in output window that 0 tests have run.
I tried to re-enable TypeMock in Visual Studio and stopped test process. Nope. Test server process does not seem to even start as long as TypeMock is enabled.
Here are extracts from TypeMock logs:
File 1 (LinkedProfilers-ProcessInvocation.exe-13.10.2006-12-58-4.out):
Logging program: C:Program FilesTestDriven.NET 2.0ProcessInvocation.exe
Cannot read EnvName0 => The system cannot find the file specified.
Reset Location: C:PROGRA~1NCoverCoverLib.dll
Adding profiler: {6287B5F9-08A1-45E7-9498-B5B2E7B02995}
Loaded C:PROGRA~1NCoverCoverLib.dll
Adding typemock profiler
Loaded C:Program FilesTypeMockTypeMock.NETMockWeaver.dll
Target Runtime .NET 2.0
Initialize Profiler 0, Target Runtime .NET 2.0
Initialize Profiler 1, Target Runtime .NET 2.0
File 2 (TypeMock-ProcessInvocation.exe-13.10.2006-12-58-4.out):
Logging program: C:Program FilesTestDriven.NET 2.0ProcessInvocation.exe
Known namespace: nunit
Known namespace: vstesthost.exe
Known namespace: MbUnit
Known namespace: TestDriven.TestRunner.dll
What can be wrong?