We have an ASP.NET webforms app that has try/catch blocks all throughout. In the catch block, it calls a method that sends an email containing limited information about the error thrown.
We want to implement ELMAH in this app, but ELMAH only works with unhandled exceptions (based on my experiences, at least). What I would like to do is, instead of removing all the try/catch blocks from the app, replace the code within the method that sends the email with a call to ELMAH that will force ELMAH to send an email as if the exception were unhandled. It would look just like the regular email, complete with stack trace, authenticated user, referring URL, etc.
If you handle the exception, ELMAH will not receive it.
ELMAH is not designed to be a full logging framework but to work alongside one, such a log4net.
Instead of trying to force ELMAH into this role, consider using a dedicated logging framework for your handled exceptions.
You can signal ELMAH from your handling code if you really need to, as described in this answer to does elmah handle caught exceptions as well: