chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
Hi


failed:
*** TypeMock.NET needs to be linked with Coverage Tool to run, to enable do one of the following:
1. link the Coverage tool through the TypeMock 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.NET topic)
TypeMock.TypeMockException
Message:
*** TypeMock.NET needs to be linked with Coverage Tool to run, to enable do one of the following:
1. link the Coverage tool through the TypeMock 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.NET topic)
Source: TypeMock
StackTrace:
at TypeMock.MockManager.Init(Boolean collectAllCalls)

that message is the same even if i use the testdrven menu test with typemock

thnks
asked by tolisss (28.8k points)

27 Answers

0 votes
Hi tolisss
Did you get my mail?
answered by ohad (35.5k points)
0 votes
hi yes i got i ll send log as soon as i can
answered by tolisss (28.8k points)
0 votes
hi again seems that the log is not created for some reason

still the message Couldn't connect to test runner process remains but no log created anywhere
answered by tolisss (28.8k points)
0 votes
Hi
what about running the test from the command line using TMockRunner?
(TMockRunner.exe MbUnit.Cons.exe test.dll)
Was it successful?
answered by ohad (35.5k points)
0 votes
haven't try that i could if u want.
but as u imagagine testdriven usability cannot compare at all to mbunit console

jamie had a remote assistance feature do u offer sush a feature?
answered by tolisss (28.8k points)
0 votes
Hi
The command line test is just to see if the problem is in the test side or in TypeMock side.
We have remote assistance which I intended to offer you.
We will set a session by mail.
answered by ohad (35.5k points)
0 votes
hi i ll try the command line and i tell u
if u send any mails to me please resend cuase somthing was very bad with my old mail. i have change it now u can see it in my userprofile
answered by tolisss (28.8k points)
0 votes
Hi All
We found a bug in our 64 bit version.
We fixed the bug and sent the patch to tolisss.
answered by ohad (35.5k points)
0 votes
thnks again for the effort and the excellent support evrything works fine now :)
answered by tolisss (28.8k points)
0 votes
I am having the same trouble.

I upgraded to Isolator 4.2.3 last week. When I did TDD.NET stopped working so I upgraded that as well. I'm now trying to run my NUnit (2.4.2.0) tests using TDD.NET (2.12.2179) and TI (4.2.3).

I get the following error:

failed: 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.Init()

If I uninstall and reinstall TI then it goes away for awhile but then comes back. I also run tests from the command-line via MSBuild. Those scripts register TypeMock.

Furthermore, if I try to run my unit tests in the debugger I get another error when MockManager.Init() is called. It indicates that it failed to load "c:\winnt\system32\tmService.dll".

Any ideas?

TIA,

Darin
answered by Darin_Creason (3.5k points)
...