Error Handling in ASP.NET MVC 5: Part 4 – Handling 404 Not Found Errors

So far in this series I have been exploring the error handling features in an ASP.NET MVC Web application from the point of view of handling internal server errors. Today I will be turning my attention to handling 404 Not Found errors.

Error Handling in ASP.NET MVC 5: Part 3 – HandleErrorAttribute and HttpApplication.Error

In the previous post I covered the Custom Errors and HTTP Errors error handling features. You can configure both of these in various ways, including specifying that your own error page should be shown when there is an error. What you do not get is complete control. Today you are going to see how you can gain that control by manually handling errors. As with the last post, I am continuing to concentrate on how 500 Internal Server Error errors can be handled.

Error Handling in ASP.NET MVC 5: Part 2 – Custom Errors and HTTP Errors

In the previous post, I covered the basics of error handling, the main error handling features available to an ASP.NET MVC Web application, and I introduced the demo Web application. You are now going to use that application to start exploring those features, initially from the point of view of dealing with the 500 Internal Server Error type.

Error Handling in ASP.NET MVC 5: Part 1 – Beginnings and the Demo Application

Some years ago I had to add error handling to an ASP.NET MVC Web application. I quickly ran into what must be many .NET developers’ experience of the process: growing confusion as to how the various features of MVC, ASP.NET and IIS are conspiring to keep me from completing the task. This tangle is memorably portrayed by secretGeek:

Error Handling in ASP.NET MVC 5: Index of Posts

This is the index of posts for the series on Error Handling in ASP.NET MVC 5.

• Part 1 — Beginnings and the Demo Application
• Part 2 — Custom Errors and HTTP Errors
• Part 3 — HandleErrorAttribute and HttpApplication.Error
• Part 4 — Handling 404 Not Found Errors
• Coming soon – Part 5 — Error Handling Strategies

Recent .NET Developments

Microsoft has been busy creating interesting new projects in the .NET world. To aid remembering which development is which, here’s a quick overview:

Neo4j versus Windows

I recently decided to have a look at what is maybe the least known of the Not Just SQL data management systems: the graph database. From my initial investigation, Neo4j looked like being the most mature and documented implementation available. However, having installed it on my shiny new Windows laptop, I found that I was getting a couple of memory-related Java exceptions when populating the graph with around a million nodes (batched, natch).

A Reminder about IIS File Protection

This is a reminder for .NET developers regarding Web site and Web service configuration files. By default, IIS protects files with the extension .config but it does not protect files with the extension .xml.

Error Handling in ASP.NET MVC 3: Part 5 – Error Handling Strategies

To date, this series has covered the main error handling features available to an ASP.NET MVC 3 Web application and how they can be used to handle 500 and 404 errors. What has been missing is how these features can be combined to create robust error handling strategies. This is what I will focus on today, in what is the last post in the series.

Error Handling in ASP.NET MVC 3: Part 4 – Handling 404 Not Found Errors

So far in this series I have been exploring the error handling features in an ASP.NET MVC Web application from the point of view of handling internal server errors. Today I will be turning my attention to handling 404 Not Found errors.