SCREENSTEPS CUSTOM ERROR PAGE CODE
SCREENSTEPS CUSTOM ERROR PAGE FREE

~/Controllers/HomeController.sc: public class HomeController : BaseController While very simple to implement, the one drawback I see in this approach is using querystring to deliver exception information to the target error page. filters.Add(new HandleErrorAttribute()) // <= disable/remove Public static void RegisterGlobalFilters(GlobalFilterCollection filters) My else is involved, other than disabling/removing filters.Add(new HandleErrorAttribute()) in FilterConfig.cs public class FilterConfig We choose to use the ViewBag to communicate the error message to the view Public ActionResult Index(string Message) / Error message to be displayed (provided via querystring parameter - a design choice) / This action represents the error page Public class ErrorController : Controller / This controller exists to provide the error page Server.TransferRequest('~/Error?Message=' + exception.Message) As an alternative, Response.Redirect could be used instead. Note that we chose to use Server.TransferRequest, which is only supported in IIS 7 and above. This will invoke our error page, passing the exception message via querystring parameter Further detail would have to be logged somewhere. it will only be practical to issue a short message. Since we are going to pass exception information to our error page via querystring, This would be a good place to log any relevant details about the exception. for additional context on use of this technique

protected void Application_Error(Object sender, EventArgs e)

SCREENSTEPS CUSTOM ERROR PAGE CODE

Throw an unhandled exception in your code and see it go to the page with id 500, and then use a URL to a page that does not exist to see 404.Д«uilding on the answer posted by maxspan, I've put together a minimal sample project on GitHub showing all the working parts.Д«asically, we just add an Application_Error method to to intercept the exception and give us an opportunity to redirect (or more correctly, transfer request) to a custom error page. Inside web.config add the following entries, under System.Web filters.Add(new HandleErrorAttribute()) Remove this filter because we want to handle errors ourselves via the ErrorPage controller public static void RegisterGlobalFilters(GlobalFilterCollection filters) Inside App_Start open up FilterConfig.cs and comment out the error handling filter. These should appear in a folder called ErrorPage. I'll put forward what I did from scratch.Д¬reate the ErrorPage controller public class ErrorPageController : ControllerДЄdd views for these two actions (right click -> Add View). There seem to be a number of steps here jumbled together. It could be easily extended to offer more detailed error info, but ELMAH handles that for me & the statusCode & statusDescription is all that I usually need.

Reason you think this link exists is because you needed to invent it.ДЄnd what did you feel when the link would not open? ДЄre you saying you have something against homosexuals?

SCREENSTEPS CUSTOM ERROR PAGE FREE

Links are equal, so if this link doesn't work for you, feel free toД®xperiment with other links that might bring you joy and fulfillment.Д«uddhist explanation. You from realizing this link's fulfillment. Not God's will for you to open this link. Please contact the system (Model != null & )Д®xception: ViewBag.Title = 'Oops! Error Encountered' causes: So Error.cshtml looks something like this: = '_Layout.cshtml' ДЄn unexpected error has occurred. I tend to add a bit of logic though, to show the stack trace and error information if the application is in debug mode. Response.StatusCode = 404 //you may want to set this to 200ДЄnd the views just the way you implement them. My current setup (on MVC3, but I think it still applies) relies on having an ErrorController, so I use: ДЄnd the controller contains the following: public class ErrorController : Controller What do I have to do to handle other errors? It does look like this is not all there is to displaying custom errors as I read through the code in the OnException method of the HandleErrorAttribute class and it is handling only 500. The default one for 500 was already available out of the box.Дeclared in each custom error page view that the model for the page is ДЇor 500, it shows the custom error page. Registered HandleErrorAttribute as a global action filter in the FilterConfig class as follows: public static void RegisterGlobalFilters(GlobalFilterCollection filters)ДЇilters.Add(new CustomHandleErrorAttribute()) Д¬reated a custom error page for each of the above messages. Here's what I have done:Д®nabled custom errors in the web.config as follows:

I want a custom error page shown for 500, 404 and 403.

Screensteps custom error page