I enjoy debugging in .net. There is so much I can figure out about what's going on in my system by placing a little red dot on a line of code to set a breakpoint. I have quite a few debugging windows at my disposal and it sure as shit beats debugging using gdb. But, there is one thing that can get under my skin with ASP.NET debugging, and that is when the debugger won't start for some reason, whether its the debug attribute in the web.config set to false or IIS being locked down and you have to go into the urlscan.ini file, it can sometimes take a lot of time to figure out why the debugger won't start. I really thought for a while, it must just be me, and there couldn't be that many ways for the debugger to not start or stop working. Boy was I wrong.
Roy Osehrove posted to his blog an article titled "Resolving Debugger Problems". This is one long list, and definitely a good resource to have if you have no idea why you can't start the debugger, or why breakpoints don't get hit anymore. This article will surely save some hair from being pulled out, especially out my head.
11:13:15 PM 
|
|
