I have the following in my web.config:
<customErrors mode="On" defaultRedirect="Error">
<error statusCode="404" redirect="Error/NotFound" />
I can see the misconception. You want to do the
MVC thing and
redirect to a controller action.
defaultRedirect is itself a
Web Form convention and thereby limited. The moment you redirect to another controller, you will lose your
HttpContext, and thereby lose your
[HandleError] Attribute requires a
View to direct its error message to. Going by your example above, I assume that you have a
Views/Error Folder for your
ErrorController, and in it you have an
Index View. If you want to your Filter Context to send a
HandleErrorInfo object to that view,
Try this syntax:
[HandleError(View="~/Views/Error/Index")] Public class HomeController : Controller
But what about Logging?!?!?
I suspect your intention is more than just displaying error stack to users. In fact, I suspect you have no such intention at all. I suspect what your real aim is to log your error (probably to db) and to display some bland message to your user.
What I've explained so far was "what is best [way to] show unhandled exceptions in my view". The
[HandleError] attribute is good for that.
But when you want to move to the next step (logging the error) you have a few options:
1) Override your base controller's On Exception method; create your own
Controller inheriting from the MVC Controller class but override the On Exception Method. This approach can be used in conjunction with [HandleError] attribute
2) Create a custom exception handler Create your own Exception Handler that logs the error. Your exception handler can then call a View of choice or can work in conjunction with
[HandleError(order=2)] since filter attributes can take an order argument applying precedence.
Nitin Sawant asks what an error view would look like. The
@model System.Web.Mvc.HandleErrorInfo <h2>Exception details</h2> <p> Controller: @Model.ControllerName </p> <p> Action: @Model.ActionName </p> <p> Exception: @Model.Exception </p>