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
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
asked by pkr (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 (3k points)