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

Migrating HTTP modules to middleware


In this recipe, we will learn how to transform an ASP.NET HTTP module in ASP.NET Core middleware.

Before anything, let's brush up on what an HTTP handler is. An HTTP module can add a treatment to an incoming request from the ASP.NET/IIS pipeline before it arrives at the handler, and/or add a treatment to the generated response. It can even transform or generate its own response.

Getting ready

We create an empty ASP.NET Core web application with Visual Studio and .NET Core or the .NET Framework.

How to do it...

We'll create a new HTTP module, and track the starting/ending point of the request. We will also add information to the beginning of the response and end of the response.

  1. First, let's see the anatomy of an HTTP module:
public class MyHttpModule : IHttpModule 
{ 
  public void Dispose(){} 
 
  public void Init(HttpApplication context) 
  { 
    context.BeginRequest += (source, args) => 
    { 
      context.Response.Write("MyHttpModule BeginRequest"...