Book Image

ASP.NET Core MVC 2.0 Cookbook

By : Jason De Oliveira, Engin Polat, Stephane Belkheraz
Book Image

ASP.NET Core MVC 2.0 Cookbook

By: Jason De Oliveira, Engin Polat, Stephane Belkheraz

Overview of this book

The ASP.NET Core 2.0 Framework has been designed to meet all the needs of today’s web developers. It provides better control, support for test-driven development, and cleaner code. Moreover, it’s lightweight and allows you to run apps on Windows, OSX and Linux, making it the most popular web framework with modern day developers. This book takes a unique approach to web development, using real-world examples to guide you through problems with ASP.NET Core 2.0 web applications. It covers Visual Studio 2017- and ASP.NET Core 2.0-specifc changes and provides general MVC development recipes. It explores setting up .NET Core, Visual Studio 2017, Node.js modules, and NuGet. Next, it shows you how to work with Inversion of Control data pattern and caching. We explore everyday ASP.NET Core MVC 2.0 patterns and go beyond it into troubleshooting. Finally, we lead you through migrating, hosting, and deploying your code. By the end of the book, you’ll not only have explored every aspect of ASP.NET Core MVC 2.0, you’ll also have a reference you can keep coming back to whenever you need to get the job done.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Creating and using an exception filter


In this recipe, you will learn how to create and use exception filters at global, controller, and action levels.

Getting ready

Let's create an empty web application with VS 2017.

How to do it...

ASP.NET Core MVC has a lot of advantages over earlier versions of ASP.NET MVC, such as ASP.NET MVC 5:

  • No more HandleError attribute usable at global, controller, or action level (so, no more customErrors attribute to parametrize in web.config)
  • No more Application_Error event in global.asax
  • No more OnException method from the base Controller class to override

Of course, we could still use try/catch blocks, but it's considered a solution that is not developer-friendly. We can avoid this solution and get a cleaner code without it.

The solutions now are:

  • Using an Exception filter (to handle exceptions in action methods)
  • Using an Exception middleware (to handle more generic errors at the application level)

An exception filter will handle exceptions from any action or filter...