DonXML thinks that Visual Studio’s Edit and Continue feature can lead to bad programming habits. I see his point, but I’m personally wouldn't mind seeing this feature come to C#

Like Don, I’m a huge advocate of component-wise testing using mock objects or service stubs to test components in isolation. However, there comes a time when you have to integrate them and make all the “real” components play together. Once you reach that phase of a project, starting up a debugging session is suddenly a non-trivial experience. Even in just simple client-server scenarios the amount of time it takes to bootstrap the system can be prohibitive (or even just really annoying). And it’s in these cases where Edit and Continue provides a real productivity boost.

I don’t want Edit and Continue to save me from stepping through needless amounts of code; I want Edit and Continue to save me from having to manually attach debuggers to 3 different processes every time I need to make a minor change during integration testing.

Updated: The status of Edit and Continue is still up in the air (at least for C#, anyway!) Didn't mean to suggest that is wasn't...