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
In addition to a scenario that I described yesterday (TypeMock 6.x) causes build on build machine hang, a combination of TypeMock and TestDriven on a local development machine also occasionally hung after executing all tests. The only way to go forward was to kill ProcessInvocation.exe.

Interestingly, the problem went away when I installed latest beta of TestDriven.NET (3.0 beta 2). Still, since there's been several reports about Isolator 6.0 behavior in combination with other products, I believe the issue has something to do with Isolator (I've been successfully using TestDriven.NET 2.24 for a long time).
asked by vagif (19.4k points)

12 Answers

0 votes
We have installed the second patch on our build machine. So far so good, but I'll know for sure tomorrow, after it will run all nightly builds.
answered by vagif (19.4k points)
0 votes
Congratulations! All nightly builds worked, coverage reports generated. Thank for the fix.
answered by vagif (19.4k points)
...