Aaarrrrgggghhhhhhh!!!!!!!

The most frustrating thing about working in Visual Studio is a process that looks like this:

1. debugging
2. realizing what you are doing wrong
3. trying to fix it "real quick" (forgive my Texan drawl, y'all )
4. trying to type while still debugging
5. being altered that you have to stop debugging before you may make C# changes

 
 

It's so frustrating. Why can't Visual Studio just automatically stop debugging when I start typing in a class? Hiss! Does anyone know how to wiggle away from this pitfall?

 
 

This post on Edit and Continue suggests that there is a way to, in limited cases, to get away from the ANNOYING dialog box that reads:

Edit and Continue: Changes are not allowed while code is running or if the option 'Break all process when one process breaks' is disabled. The option can be enabled in Tool, Options, Debugging.

 
 

...which is specifically referring to a checkbox in the "General" subsection of Debugging, but checking this checkbox, does not make my life easier. I either still see the dialog box above or I see another one reading:

Edit and Continue: Changes are not allowed in the following cases:

• When the debugger has been attached to an already running process.
• The code being debugged was optimized at build or run time.
• The assembly being debugged is loaded as domain-neutral.
• The assembly being debugged was loaded through reflection.

 
 

The second dialog box doesn't make me feel any better. You know, y'all?