Customizing ASP.NET Core Part 03: Dependency Injection

In the third part of this series, we'll take a look into the ASP.NET Core dependency injection and how to customize it to use a different dependency injection container if needed.

The Series Topics

• Customizing ASP.NET Core Part 01: Logging
• Customizing ASP.NET Core Part 02: Configuration
• Customizing ASP.NET Core Part 03: Dependency Injection - This article
• Customizing ASP.NET Core Part 04: HTTPS
• Customizing ASP.NET Core Part 05: HostedServices
• Customizing ASP.NET Core Part 06: MiddleWares
• Customizing ASP.NET Core Part 07: OutputFormatter
• Customizing ASP.NET Core Part 08: ModelBinder
• Customizing ASP.NET Core Part 09: ActionFilter
• Customizing ASP.NET Core Part 10: TagHelpers

Why Use a Different Dependency Injection Container

In the most projects, you don't really need to use a different dependency injection Container. The DI implementation in ASP.NET Core supports the basic features and works well and pretty fast. Anyway, some other DI containers support some interesting features you may want to use in your application.

from DZone.com Feed https://ift.tt/2xLGgI6