Custom Error Page in asp.net mvc 3

Question

I have a new asp.net mvc 3 website with the razor engine and am trying to get the site ready for production where I cannot have the Yellow Screen of Death come up. In webforms this is easy, just turn on customErrors in the web.config and you are done.

To test I setup a test controller method as such:

    public ActionResult Ex()
    {
        throw new InvalidOperationException();
    }

I expected the error view (/Views/Shared/Error.cshtml) to be displayed instead I get the Yellow Screen of Death with the message "Operation is not valid due to the current state of the object." I tried turning on customErrors in the web.config and it still does not work. I am calling the RegisterGlobalFilters method in the Global.asax but have also tried applying the HandleError attribute directly.

Thanks for your help.

The message you are seeing is expected with CustomErrors turned on - what happened with CustomErrors turned off? — Greg Sansom
– Greg Sansom, Commented Jun 7, 2011 at 0:04

37Stars · Accepted Answer · 2011-06-30 05:06:42Z

12

Turn on the custom errors and route them to an Error controller.

<customErrors mode="On" defaultRedirect="~/Error/Unknown">
  <error statusCode="403" redirect="~/Error/NoAccess" />
  <error statusCode="404" redirect="~/Error/NotFound" />
</customErrors>

The controller needs the actions Unknown, NoAccess, and NotFound. Each will need to return a view.

answered Jun 30, 2011 at 5:06

37Stars

2,49920 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Custom Error Page in asp.net mvc 3

1 Answer 1

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Linked

Related