This post originated from an RSS feed registered with .NET Buzz
by Frans Bouma.
Original Post: Why Edit & Continue is a bad thing
Feed Title: Frans Bouma's blog
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/fbouma/Rss.aspx
Feed Description: Generator.CreateCoolTool();
Let me quote myself from a usenet posting I did on Edit & Continue in C#:
Afaik, E&C is not planned for vs.net 2004 [C#], and frankly I'm happy about it, because the [C#] devteam can spend that time on other, more valuable features :). (E&C IMHO creates bad debugging styles. Debugging isn't about trial & error which is the implication of E&C. It's about thinking through where teh bug can be, fire up the debugger to test your thoughts, then think about a fix, think through the change implications and fix it. Test it and if it fails again, start the debugger to see why. This way you save a lot of time, instead of poking around in the code inside the debugger :) )
In short: a good debugging-style doesn't need nor require Edit & Continue. If you do need it, it's time to take a step back and look at what you're doing when you're debugging. 10 to 1 you can save yourself a lot of time by thinking first and acting later instead of the reverse.
Previous Topic
