This post is in response to a question from a reader about how library authors can ensure consumers of their library insert the library's middleware at the right point in the app's middleware pipeline. Unfortunately, there's not really a great solution to that (with a couple of exceptions), but this post highlights one possible approach.

Usually, when getting errors logged through MEL, all of the HTTP context data is logged as part of the error, making it easy to spot why an error happened or at least making it a lot easier recreating the error. Today's error didn't include much more information than an error message and a request-id.

Ideally, we would never have to take our site offline to do maintenance. All of our deployments would happen smoothly, and we could transition seamlessly into our new set of features. Once in a while it just isn’t possible, and we have to stop our users from interacting with our application. With IIS, you can drop an app_offline.htm file in the root of your site, but this requires the deployment of a file to your production environment. It works, but it isn’t great.

In this post, we’ll learn about Middleware and how to create them. Middleware is a software component which is executed on every request and response in ASP .NET Core application.

To provide access or deny, we have to get the IP Address of the incoming request. We need to verify that against a list. When I say list, you can use this list to grant or deny access. This is called as IP Whitelisting and Blacklisting respectively using middleware

Simply, middleware is code that becomes part of a pipeline to handle requests and responses in a web app. In ASP.NET Core, middleware is a big deal! All requests are handled by a pipeline of middleware.

Detect Blocking Calls in ASP.NET Core Applications. Blocking calls can lead to ThreadPool starvation. Outputs a warning to the log when blocking calls are made on the ThreadPool.

A developer toolkit for building SaaS applications http://saaskit.net Blog post on how to use SaaS kit https://benfoster.io/blog/tagged/saaskit