What steps will reproduce the problem?
1. Add the sample page to a Web Application project that has elmah set-up.
2. Run the sample page (unhandled exception occurs in a background thread)
3. Go in the elmah.axd error listing page
Expected results:
4. A new error matching the background thread exception has been logged.
Actual results:
4. No new errors has been logged.
What version of the product are you using? On what operating system?
I am using elmah v1.1.11517.2009 on Windows XP SP3.
The project I extracted the sample page from is a Web Application project
built using .Net 3.5 in Visual Studio 2008 SP1.
The Web.config file is the default one created with a new project + the
required elmah configurations to support email and SQL Server logging (the
same project and same config file has been used to successfully log other
types of exceptions supported by elmah).
No filtering of exceptions is done.
Other information:
I have been able to capture this exception by creating an HTTP Module that
is hooked on the AppDomain.CurrentDomain.UnhandledException event. This
event is triggering when the unhandled exception occurs in the thread.
Maybe elmah could hook itself on Domain.UnhandledException event to capture
everything? Or, is there drawbacks/issues to using that handler?
Original issue reported on code.google.com by edgard.p...@gmail.com on 16 Dec 2009 at 9:14
Original issue reported on code.google.com by
edgard.p...@gmail.comon 16 Dec 2009 at 9:14Attachments: