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
I had VS2010, installed Typemock 7.0.9 to make sure all was working before installing 2012. Installed 2012, and the tests run fine by themselves, but when I try to get code-coverage (which re-runs the tests) I get an error. Re-installed Typemock 7.0.9, tests still won't run with code-coverage.

Test error is (and Visual Studio 2012 doesn't let me copy and paste, so I'm summarizing):

threw exception: Sytem.TypeInitializationException: The type initializer for 'f5' threw an exception. ---> System.TypeInitializationException: The type type intitializer for 'TypeMock.InterceptorsWrapper' threw an exception. ---> TypeMock.TypeMockException: ** Typemock Isolator is not currently enabled. To enable do one of the following:

* To run Typemock Isolator as part of an automated process you can:
- run tests via TMockRunner.exe command line tool
- use 'TypeMockStart' tasks for MSBuild or NAnt

* To work with Typemock Isolator inside Visual Studio.NET: set Tools -> Enbable Typemock Isolator from with Visual Studio

To be clear, Typemock is listed in the Add-in Manager, checked and checked for Startup as well.
asked by boo (21.8k points)

12 Answers

0 votes
Hi,

I'll contact you via Email.
answered by NofarC (4k points)
0 votes
When can I expect to see that email? I have not seen anything yet. Thanks!
answered by boo (21.8k points)
0 votes
Hi,

I sent the Email on Sunday, sorry to hear you didn't get it.

Anyway, I'll send it again via Gmail, please let me know if you get it.
answered by NofarC (4k points)
0 votes
I am having the exact same problem. I'm using VS 2012 and Typemock 7.1.6.0. What's the fix for this?
answered by mjkoskinen (300 points)
0 votes
I had VS2010, installed Typemock 7.0.9 to make sure all was working before installing 2012. Installed 2012, and the tests run fine by themselves, but when I try to get code-coverage (which re-runs the tests) I get an error. Re-installed Typemock 7.0.9, tests still won't run with code-coverage.

Test error is (and Visual Studio 2012 doesn't let me copy and paste, so I'm summarizing):

threw exception: Sytem.TypeInitializationException: The type initializer for 'f5' threw an exception. ---> System.TypeInitializationException: The type type intitializer for 'TypeMock.InterceptorsWrapper' threw an exception. ---> TypeMock.TypeMockException: ** Typemock Isolator is not currently enabled. To enable do one of the following:

* To run Typemock Isolator as part of an automated process you can:
- run tests via TMockRunner.exe command line tool
- use 'TypeMockStart' tasks for MSBuild or NAnt

* To work with Typemock Isolator inside Visual Studio.NET: set Tools -> Enbable Typemock Isolator from with Visual Studio

To be clear, Typemock is listed in the Add-in Manager, checked and checked for Startup as well.


I am having the exact same problem. I'm using VS 2012 and Typemock 7.1.6.0. What's the fix for this?
answered by mjkoskinen (300 points)
0 votes
Hi mjkoskinen,

Which code cover tool do you use?
answered by alex (18k points)
0 votes
Hi mjkoskinen,

Which code cover tool do you use?


The one built into VS 2012
answered by mjkoskinen (300 points)
0 votes
Hi,

Can you please try installing this patch?

https://www.typemock.com/files/patches/T ... verage.msi


Notice that you don't need to link Typemock Isolator to VS 2012.

Looking forward for your feedback!
answered by NofarC (4k points)
0 votes
Hi,

Can you please try installing this patch?

https://www.typemock.com/files/patches/T ... verage.msi


Notice that you don't need to link Typemock Isolator to VS 2012.

Looking forward for your feedback!


I installed the patch. With the patch installed none of the tests pass successfully regardless of whether I run with or without code coverage on. However, if I do run with code coverage on I can see its coverage even though the test still fails.
answered by mjkoskinen (300 points)
0 votes
Hi,

Thank you foor the feedback.

Do you get a message explaining why the tests fail?
answered by alex (18k points)
...