Learning dependency injection in ASP.NET Core

To give you a bit of a background, before .NET Core existed, the only way to get DI in your applications was through the use of third-party frameworks such as Autofac, LightInject, Unity, and many others. The good news is that DI is now treated as a first-class citizen in ASP.NET Core. This means that you don't need to do much to make it work.

The built-in Microsoft DI container does have its limitations though. For example, the default DI doesn't enable advanced capabilities, such as property injection decorators, injections based on name, child containers, convention-based registration, and custom lifetime management. So, if you can't find features that you're looking for available in the default DI container, you'll need to consider other third-party DI frameworks mentioned earlier as an alternative. However, it is still recommended to use the default DI framework for building ASP.NET Core applications that...