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
Ask a question
The Unit Testing Company
Development Resources
Knowledge Base
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.

Related questions

No longer debug via TestDriven since upgrading from v4

0 votes
After upgrading to the latest version of TypeMock I can no longer use the 'Test with debugger' feature. At the first attempt to mock, e.g. using the old MockManager.MockAll api I get a nullreferenceexception. I've already talked to TestDriven and they have remotely run my tests on my machine and believe it is a problem with TypeMock's handling of the attached debugger.

Possibly related to http://typemock.com/community/viewtopic.php?t=1354
asked by pkr
Report User
 (3k points)

1 Answer

0 votes
I think I spotted the confusion. I almost always run with Break On All CLR Runtime exceptions. It would appear that TypeMock now throws some internal exception and then catches it before continuing. Consequently I'm now getting false positives as I'm trying to debug.
answered by pkr
Report User
 (3k points)
...

Products

Help

Company

Community

Contact

Typemock Store (US toll FREE 866–895–4680). Copyright © 2006 Typemock Inc. All rights reserved. Terms of Use.