Edit and Continue
One of the best things you can do is to change your development work process:
Do most of the development in the IDE. Ideally, most of the design work/program logic/etc. would be done before you write a single line of code.
Debug only to confirm operation is as designed.
Don't debug to figure out what method to call, or what properties are available. Use the documentation and Intellisense.
Walk through the content logically at regular intervals to see if it makes sense. If you have difficultly, chances are things need breaking into smaller pieces.
Create tests for important conditions, and implement try/catch for potentially critical problems, so you don't get kicked out mid-debug.
When you do find a problem during debugging don't exit, continue through and see what else needs tweaking.
Identifying exploits like loops, common methods, and objects early on is better than trying to refactor later.
Edit and Continue is nice, but don't let it become a crutch.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
