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

Introduction


Filters are code injected into request processing. There can be many categories of filters: authorization, caching, logging, exception, and more. The filters are executed after ActionInvocation, and after the middleware is executed on the ASP.NET Core pipeline.

Here is the filter pipeline from the official ASP.NET Core documentation:

They can be applied at action or controller level as attributes, or at application level as global filters added in the global filter list in Startup.cs.

We can also control the order in which filters are executed on the same action.

We can create synchronous and asynchronous filters, but we should never mix both to avoid side effects.

There are predefined filters, and there are filters we create:

  • Predefined filters (they are used at action and controller levels):
    • [AllowAnonymous]
    • [Authorize]
    • [FormatFilter]
    • [TypeFilter(typeof(MyFilterAttribute))]
    • [ServiceFilter(typeof(MyFilterAttribute))]
  • Filters we create (global or not):
    • Action filters (deriving from IActionFilter...