All applications should have error handling. This we all know. We can't always be notified of an unhandled error (and usually aren't) when one occurs on a client's machine. The advantage we have on the Web is that we can always be notified when an unhandled error occurs. With the advent of ASP.NET, there are some great new ways to handle errors. There are some differences in .NET in not only how to handle the error, but how the information is provided to you. For example, classic ASP uses Server.GetLastError to return an ASPError object. You can and should still use Server.GetLastError in .NET, but this now returns a type System.Exception. I must give Microsoft credit for making almost everything consistent in .NET, which is quite a welcome change.

Other Headlines from 15seconds.com ...
 - The .NET Architect: Enterprise Template Overview
 - Web Application Error Handling in ASP.NET
 - Introduction to the .NET Speech SDK
 - Tracking Visitors with ASP.NET

Click here for more 15seconds.com headlines

More Tutorials Headlines ...
 - Basics of Cookies in ASP.NET
 - Give Your .NET-based Application a Fast and Responsive UI with Multiple Threads
 - Build Hyperlinks into Your Client App with the Windows Forms LinkLabel Control
 - Force ASP.NET Apps to Keep-Alive
 - Preview and Print from Your Windows Forms App with the .NET Printing Namespace