ELMAH和ASP.NET MVC异常管理 [英] ELMAH and Exception Management in ASP.NET MVC

问题描述

我在看移动从异常管理应用程序块的企业库中走了一个新的ASP.NET MVC的网站。

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

斯科特Hansleman对ELMAH博文已引起了我的眼睛，但我不完全理解的方式。通常我会想喝preSS一些例外（那些是可恢复的），在中央存储库记录它们，然后显示一个信息给用户适当的。

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似乎集中在，几乎所有未处理的异常记录。什么异常我想要处理？我可以使用相同的资源库，有所有异常一个中央位置？

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?

如何在他们的应用程序中使用ELMAH人，是正在实施的唯一的例外处理的解决方案，或者是配合使用另外一种解决方案？

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?

推荐答案

已经有一段时间，因为这是问过，但也有一些解决方案，在那里为这样的：

Been a while since this was asked, but there are a few solutions out there for this:

1. New Relic的主要集中在应用程序的性能，但不会未处理的异常。


2. codeAlert 只集中在异常处理和报告 - 为您提供您正在寻找的粒度做全球对个别例外的中央资料库。


3. preemptive 另一个应用程序的性能，但有例外的支持。

1. New Relic Mostly focused on application performance, but does unhandled exceptions.
2. CodeAlert Solely focused on exception handling and reporting - gives you the granularity you're looking for to do global vs. individual exceptions to a central repository.
3. Preemptive Another application performance app, but with exception support.

这篇关于ELMAH和ASP.NET MVC异常管理的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！