Tue, 14 Jun 2005 10:00:00 GMT
Errors happen. But in production, error logs often provide little or no help in pinpointing the exact line of code in which the problem originates. You can't usually isolate the root cause by modifying code in a production environment because recreating the exact sameenvironment is very difficult due to the large number of potential software and hardware configurations. This article provides some concrete steps you can take to get at the heart of the problems in your production code.
Interop - Get Seamless .NET Exception Logging From COM Clients Without Modifying Your Code
Tue, 14 Dec 2004 10:00:00 GMT
Using .NET objects from ASP can help you gain experience with the .NET Framework before migrating to ASP.NET. Your ASP pages will make use of the new .NET components through COM-callable wrappers (CCW). But how will you handle exceptions? This article fills you in.