ASP.NET Core – Update To Autofac 4.6.1 Recommended – More Than A Bugfix Release
If you are using Autofac in your ASP.NET Core application then I recommend to update Autofac to version 4.6.1.
If you are using Autofac in your ASP.NET Core application then I recommend to update Autofac to version 4.6.1.
In the previous post “ASP.NET Core in production: Take back control of your web app” I mentioned that getting hold if the dependency injection (DI) is just one step of many to improve the architecture of your web applications. Today well will look into 2 other aspects that are best explained together: graceful shutdown and reacting to aborted requests.
If you register a type as a singleton then you expect just 1 instance of this type in your whole application. What you may not know is that ASP.NET Core is creating 2 instances of IServiceProvider
during building of the IWebHost
that may lead to 2 instance of your “singleton”.
After working with the new ASP.NET Core server Kestrel
and the HttpClient
for a while in a number of projects I run into some performance issues. Actually, it was a throughput issue.
It took me some time to figure out whether it is the server or the client responsible for the problems. And the answer is: both.
If you are planing to run an ASP.NET Core application with IIS then this blog post might be worth a glance.
These are a few issues I run into …
After several years of using the same Dependency Injection (DI) framework like Autofac you may have a good understanding how your components, implementing the interface IDisposable, are going to be disposed.