WYSIWYG: Handling Unhandled Exception Asp.NET MVC

Well, having unhandled exception is bad in the first place but displaying user a default IIS broken exception page or the yellow broken code page is even worse. Not a good user experience. But as all code/software there is always bugs and all ways a edge case that breaks unexpectedly. These unhandled expections can be handled in controller level in Asp.NET MVC. Following is a code snipped of handling errors and routing the user to a more user friendly error page.

public class HandleErrorAttribute: System.Web.Mvc.HandleErrorAttribute
{
 public override void OnException(ExceptionContext filterContext)
 {
  string askerUrl = filterContext.RequestContext.HttpContext.Request.RawUrl;
 
  Exception exToLog = filterContext.Exception;
  exToLog.Source = string.Format("Source: {0}{1}Requested Path: {2}{1}", 
    exToLog.Source, Environment.NewLine, askerUrl);
 
  //log your message somewhere
  Handle(exToLog); 
 
  filterContext.ExceptionHandled = true;
  filterContext.Result = new System.Web.Mvc.RedirectResult("~/Error");
 
  base.OnException(filterContext);
         }
}
 
namespace YourNameSpace
{
    [HandleError]
    public class YourController : Controller
    {
        //controller code - Actions
    }
}