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
0 votes
I recently stumbled over what seems like it could be a bug in TypeMock: When TypeMock 3.7.1 is linked with NCover 1.5.8 all .Net 2.0 processes started from VS2005 crashes. II7 will hang when I attempt to debug ASP.Net pages, the internal VS2005 web server also crashes and when pressing F1 the help pops up and closes again.

Running my ASP.Net app in IIS directly from Internet Explorer works fine. If I start the development server from the command prompt it does not crash. And if I launch the help from the start menu it does not crash either.

Unlinking NCover fixes the problem. I have not tested with other versions than TypeMock 3.7.1 and NCover 1.5.8. The x64 version of TypeMock is installed.

From the event log:
- <Event xmlns="">
- <System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1023</EventID>
<TimeCreated SystemTime="2007-05-10T11:39:06.000Z" />
<Security />
- <EventData>
<Data>.NET Runtime version 2.0.50727.312 - Fatal Execution Engine Error (7A062A61) (80131506)</Data>
asked by halstein (8.7k points)

11 Answers

0 votes

I just wanted to let you know that the integration issue using the //pm flag was solved by the NCover team . The Fix was included in the new NCover 2.0.1 release and we have successfully verifed that it indeed solves the issue you had.

I would like to thank you for your patience.
answered by lior (13.2k points)