Debugging Tip
For various reasons, I often finds myself writing code that is called by other applications, often with various unexpected side results. This include IIS, various compilers, build providers, VS, etc.
In nearly every case, trying to attach to the process and then placing a break point in my code is going to be very hard. For that, I reserve the following wonderful statement:
System.Diagnostics.Debugger.Break();
This simply force a debugger to be opened on the current line. It also serve as a fast conditional break point for various cases. Tremendously helpful in many situations.
Comments
Comment preview