Error handling and logging in ASP.NET

Question

I have the following requirements for a web app, that consist of MVC 5 pages and WebApi 2 services:

All errors (404, 500, "A potentially dangerous Request.Form value was detected from the client") should produce corresponding error pages in place (no browser redirect, keep the URL the user entered in the address bar).
All error pages should be rendered using dynamic MVC views and contain a unique ID, that the user can give to phone support.
All errors must be logged, the log entries should contain the Id given to the user.
Produce different error pages for different exceptions, e.g. /error/NoSignal for NoSignalException.

Is this doable?

possible duplicate of Logging errors in ASP.NET MVC

Nick DeVore
– Nick DeVore

2014-02-07 20:06:21 +00:00
Commented Feb 7, 2014 at 20:06 — Nick DeVore
– Nick DeVore, Commented Feb 7, 2014 at 20:06

Aleksej Vasinov · Accepted Answer · 2014-02-07 20:04:18Z

1

I would override exception hangling method - in each controller or in base (depends on your decision).

    protected override void OnException(ExceptionContext filterContext)
    {
        filterContext.Exception.ToString(); // - make any checks here

        // If method is not implemented
        if (filterContext.Exception.GetType() == typeof(NotImplementedException))
        {
            filterContext.Result = new ViewResult { ViewName = "NotImplemented" };
            filterContext.ExceptionHandled = true;
        }
    }

answered Feb 7, 2014 at 20:04

Aleksej Vasinov

2,80730 silver badges29 bronze badges

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

Collectives™ on Stack Overflow

Error handling and logging in ASP.NET

1 Answer 1

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Linked

Related