A Visual Studio 2008 solution, x86 and x64 installers detailed in KB911816: Unhandled exceptions cause ASP.NET-based applications to unexpectedly quit in the .NET Framework 2.0, to get exception details with stack trace in the event log instead of entries like
"clr20r3; w3wp.exe; 6.0.3790.1830; 42435e74; system.data; 2.0.0.0; 4333a5ee; 230d; 2c; system.data.sqlclient.sql; NIL." or
"EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 appweb7437ep-9, P5 0.0.0.0, P6 433b1670, P7 9, P8 a, P9 system.exception, P10 NIL. "

x86 (32-bit) installer: UnhandledExceptionModuleSetup.msi
x64 (64-bit) installer: UnhandledExceptionModuleSetup.x64.msi

To use the module after runinng the installer, put the following in the web.config of the site in the <system.web> <httpModules> section:
<add name="UnhandledExceptionModule" type="WebMonitor.UnhandledExceptionModule, UnhandledExceptionModule, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8ddf595cb79edd99" />

Although it is a Visual Studio 2008 solution, the project is set up so that it targets the .Net Framework 2.0 - .NET 3.5 is not required on the target machine.

Last edited Jan 1, 2009 at 10:57 PM by AndrasVass, version 14