...with this line of output: The program ' JetBrains.ReSharper.TaskRunner.CLR4.MSIL.exe: Managed (v4.0.30319)' has exited with code 0 (0x0). Has anyone else seen this happening and found a workaround?
This is currently happening every time I debug code from the R# unit test runner. Over the last few weeks it has been happening every now and again (maybe 25% of the time when debugging, and usually for the first time you debug a test, then OK afterwards) - but now it is constant.
Steps to reproduce: make a unit test (NUnit based, in this case) that fails, set a breakpoint in app code, go to unit test session tab and debug the unit test that is failing. Code then executes up to the breakpoint. After this, while stepping through or over code using F10 and/or F11, the debugger will suddenly stop (at different lines, never on the same line). Sometimes this is after just a couple of steps, sometimes after a dozen or more.
I did a search for this online and a similar issue was reported against Visual studio 2010 here (http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/99b5c47c-c42a-4d24-8843-3be486c359c2/) but I have already verified that I have the setting mentioned there.
If anyone has any ideas, I would be greatly obliged to them.
Windows 7 32 Bit
JetBrains ReSharper 6.1 C# Edition
Build 126.96.36.199 on 2011-12-20T21:15:24
Visual Studio 10.0.30319.1.
PS - Resharper is normally really acecakes, this is the first issue I've ever had using it in about 2 years of use.