Using a different dependency injection container
In most projects, you don't really need to use a different dependency injection (DI) container. The existing DI implementation in ASP.NET Core supports the main basic features and works both effectively and quickly. However, some other DI containers support a number of interesting features you might want to use in your application:
- Ninject allows you to create an application that supports modules as lightweight dependencies; for example, modules you might want to put into a specific directory and have them be automatically registered in your application.
- You might want to configure the services in a configuration file outside the application, in an XML or JSON file instead of in C# only. This is a common feature in various DI containers, but not yet supported in ASP.NET Core.
- Perhaps you don't want to have an immutable DI container because you want to add services at runtime. This is also a common feature in...
