This post originated from an RSS feed registered with .NET Buzz by Scott Watermasysk. Original Post: Error Logging Modules And Handlers Feed Title: ScottW's ASP.NET WebLog Feed URL: /error.aspx?aspxerrorpath=/blog/rss.aspx Feed Description: ASP.NET and Blogging Latest .NET Buzz Posts Latest .NET Buzz Posts by Scott Watermasysk Latest Posts From ScottW's ASP.NET WebLog

Scott Mitchell and Atif Aziz have published an article, "Using HTTP Modules and Handlers to Create Pluggable ASP.NET Components" on MSDN. The sample they create enables to quickly and easily log errors in an ASP.Net application.

The Error Logging Modules And Handlers (ELMAH)...demonstrates an easy means to add error logging capabilities to an ASP.NET Web application. ELMAH illustrates how HTTP modules and handlers can be used to provide a high degree of componentization for code that is orthogonal to the Web application (such as application-wide logging). ELMAH is a truly pluggable solution, meaning that it can be dynamically added to a running ASP.NET Web application without any need for recompilation or redeployment.

If you are running a web application and not logging your exceptions, it looks like you could be up in running in just a couple of minutes.

Scott/Atif also link to a nice blog post by Rick Strahl, "Making sense of ASP.Net Paths" which summarizes various ASP.Net path/url info:

ASP.Net a plethora of properties to retrieve path information about the current request, control and application. To keep things straight I thought it'd be a good idea to summarize those options briefly along with describing some common scenarios of how they might be used.