One problem we have been encountering for nearly a year is a problem which reports ASP.NET errors, but actually does not cause any problems for the user. The error looks like this: ** Events ** --------------- Event code: 3005 Event message: An unhandled exception has occurred. Event time: 3/23/2010 11:44:44 AM Event time (UTC): 3/23/2010 11:44:44 AM Event ID: 6be66d016f1e43b48adbd638e202c698 Event sequence: 3548 Event occurrence: 1 Event detail code: 0 Process information: Process ID: 7872 Process name: aspnet_wp.exe Account name: WEBSITE\ASPNET Exception informat... [More]

After running an FxCop through one of my projects, I recently noticed that there was a newer entry for exception handling, detailing that I should no longer use the ApplicationException as it has become "useless". This contradicts my article on Exception handling which has been updated accordingly. Read this article for more information: http://blogs.msdn.com/kcwalina/archive/2006/06/23/644822.aspx

There is so much useful stuff to learn about through the MCTS path. Don't you just hate having to write a common functionality class that e-mails you with errors? Well, you've wasted your time, as ASP .NET 2.0 does this for you without you writing a single line of code. Here is what you do: 1) Add a health monitoring section <configuration>    <system.web>       <healthMonitoring enabled="true" heartbeatInterval ="0">       </healthMonitoring>   </system.web> </configuration> 2) Add a providers section inside the health monitoring to ale... [More]

I have written an article on the best way to catch exceptions. If you are wondering what structure to take when laying out your exceptions, or some hints on improving debugging, check it out! http://blogs.bdnet.co.uk/dominicz/archive/2007/04/19/Catching-exceptions-correctly.aspx