Book Image

Mastering ASP.NET Web API

By : Mithun Pattankar
Book Image

Mastering ASP.NET Web API

By: Mithun Pattankar

Overview of this book

Microsoft has unified their main web development platforms. This unification will help develop web applications using various pieces of the ASP.NET platform that can be deployed on both Windows and LINUX. With ASP.NET Core (Web API), it will become easier than ever to build secure HTTP services that can be used from any client. Mastering ASP.NET Web API starts with the building blocks of the ASP.NET Core, then gradually moves on to implementing various HTTP routing strategies in the Web API. We then focus on the key components of building applications that employ the Web API, such as Kestrel, Middleware, Filters, Logging, Security, and Entity Framework.Readers will be introduced to take the TDD approach to write test cases along with the new Visual Studio 2017 live unit testing feature. They will also be introduced to integrate with the database using ORMs. Finally, we explore how the Web API can be consumed in a browser as well as by mobile applications by utilizing Angular 4, Ionic and ReactJS. By the end of this book, you will be able to apply best practices to develop complex Web API, consume them in frontend applications and deploy these applications to a modern hosting infrastructure.
Table of Contents (14 chapters)

Migrating HTTP modules to middleware

Prior to ASP.NET Core, the ASP.NET world had concepts of HTTP Handlers and HTTP Modules. They were part for request pipeline, having access to life cycle events throughout the request.

They are similar to the concept of Middleware in ASP.NET Core. In this section, we will migrate the HTTP module to ASP.NET Core middleware.

Writing HTTP modules and registering them in web.config is out of the scope of this book; we will refer to this MSDN article, Walkthrough: Creating and Registering a Custom HTTP Module (https://msdn.microsoft.com/en-us/library/ms227673.aspx), and migrate to ASP.NET Core middleware.

To summarize the article--the HTTP module appends a string to the start and end of response when request of file extension is .aspx.

Create C# class AspxMiddleware that does look for the request that contains the PATH which contains .aspx. If present...