Edit and proceed with TestDriven.NET and Gallio
I have VS08sp1, Gallio 3.0.6.763 and TestDriven.NET 2.14. I am using MBUnit framework for unit tests. When using TestDriven Test With> Debugger, I can step into the code. However, I am unable to "Edit and Continue" despite having this option enabled in VS options. The following error message appears:
changes are not allowed when the debugger is attached to an already running process
The project the unit is testing is a Windows class library and I can "Edit and Continue" when running the library through a normal debugger. I would appreciate any help getting "edit and keep" working.
Thanks!
a source to share
From http://www.testdriven.net/downloads/releasenotes.html :
705: Add (hidden) support for 'Test C ... E&C'
To enable 'Test With ... Debugger (E&C)' which works with Edit & Continue; edit TestDriven.dll.config file and uncomment. This test runner can "touch" project files when used with source control (which is why it is disabled by default).
a source to share
I don't think you can make this work with TestDriven.Net unless Jamie changes the ProcessInvoker.exe startup process, so the edit and continue work will work.
To be honest, I always turn off Edit and Continue because it has so many restrictions that it is practically useless for me. Instead, I rely on the Visual Studio Immediate Window to experiment with running applications and prototype fixes.
Another benefit of disabling Edit and Continue, along with Require source files to match the original version exactly, is that the debugger no longer locks the source files. This is especially handy as I can fix two or three errors in one session, and it sucks to stop the debugger to edit files. In addition, Visual Studio seems to spend quite a lot of time redrawing tabs as it turns on or off the "locked" status, especially if there are many open tabs. I have seen pauses a few seconds before and after debugging as a direct consequence of blocking. Hence, disabling all functions that cause blocking provides noticeable speed.
So, I think my advice is to try a different approach to debugging your tests that doesn't require editing and continuing.
a source to share