In this section, we are going to build our own middleware extensions and try to utilize the same in our code. I have created one folder for the same. Below is the glimpse for the same.

I have created one sample middleware and below is the snippet for the same.

Here, first thing comes constructor which has the reference of RequestDelegate next. This means this component will be able to invoke next middleware in the pipeline. After constructor, we have definition which allows us to invoke our middleware.  Here, we have very simple custom middleware class. Now, in order to use the same in our application with appBuilder extension methods, we need to expose the same as extension. Therefore, Let’s go ahead and write extension for the same. Extensions, I’ll be keeping in a separate folder just for the sake tidiness.  Now, my folder structure goes like this.

And my extension method which I have written on top of IApplicationBuilder just to make sure that it should be available like other extension methods.

Off-course,  I am using one generic method to return my custom middleware here “UseMiddleware<>“. With that being said, let’s consume the same in our app.

With above changes done, when I run my app, it will come something like this.

However, when I run some other middlewares like MapWhen, then it will produce following output.

I hope middleware chaining is clear now. In coming sections, we will delve further. Thanks for Joining me.

Thanks,
Rahul Sahay
Happy Coding

Share

Send this article by email

What is your name?

Please indicate below the emails to which you want to send this article: Understanding Middleware in ASP.NET Core - Part 3

Enter one email per line. No more than 5 emails.

Send

Close