asp.net-mvc - ELMAH and Exception Management in ASP.NET MVC

Question

I am looking at moving away from the Exception Management Application Block in the Enterprise Library for a new ASP.NET MVC site.

Scott Hansleman's post(s) on ELMAH has caught my eye but I don't fully understand the approach. Typically I would suppress some exceptions (ones that are recoverable), log them in a central repository, and then display a message to the user as appropriate.

ELMAH seems focused on, "Logging of nearly all unhandled exceptions.". What about exceptions I want to handle? Can I use the same repository so there is one central location for all exceptions?

How are people using ELMAH in their applications, is it the only exception handling solution being implemented, or is it used in conjunction with another solution?

Answer 1

自从有人问这个问题以来已经有一段时间了，但是有一些解决方案：

1. New Relic主要关注应用程序性能，但会处理未处理的异常。
2. CodeAlert 仅专注于异常处理和报告 - 为您提供所需的粒度，以便对中央存储库执行全局异常与个别异常。
3. Preemptive另一个应用程序性能应用程序，但支持异常。