Here's another neat trick I learned:
System.Diagnostics.Debugger.Break()
programatically causes the debugger to break on the next instruction. The really nice part is, this also works for a program compiled in Release mode, without debugging information.
