Handling Assertions in ASP .NET Web AppsRecently I was moving along with my ASP .NET Web site de-sign and was quite pleased to see just how much easier ASP .NET made the whole process. Being a good boy, I went through the design process and was about to start development when I noticed a small problem. A prototype I developed to test a theory would hang when I used the standard Debug.Assert.
If you hearken back to the February 2001 Bugslayer column, you'll remember that I talked about the TraceListeners, which do the actual output for the System.Diagnostic namespace's Debug and Trace objects. In that column, which I wrote back in the dark ages of the 2000 PDC release of the Microsoft® .NET Framework, I mentioned that the DefaultTraceListener would pop up a message box on assertions only when running with an interactive user logged in.