Microsoft.Extensions.DependencyInjection vs Ninject

Developers should learn and use this library when building meets developers should learn ninject when building . Here's our take.

Microsoft.Extensions.DependencyInjection

Nice Pick

Developers should learn and use this library when building

Pros

• NET applications, especially ASP
• Related to: asp-net-core, c-sharp

Cons

• Specific tradeoffs depend on your use case

Ninject

Developers should learn Ninject when building

Pros

• NET applications that require maintainable, testable code through dependency injection, such as in enterprise-level web services, desktop applications, or complex business logic systems
• Related to: dependency-injection, inversion-of-control

Cons

• Specific tradeoffs depend on your use case

The Verdict

These tools serve different purposes. Microsoft.Extensions.DependencyInjection is a library while Ninject is a framework. We picked Microsoft.Extensions.DependencyInjection based on overall popularity, but your choice depends on what you're building.

The Bottom Line

Microsoft.Extensions.DependencyInjection wins

Based on overall popularity. Microsoft.Extensions.DependencyInjection is more widely used, but Ninject excels in its own space.