Ninject
the ninja of .net dependency injectors (by ninject)
DryIoc
DryIoc is fast, small, full-featured IoC Container for .NET (by dadhi)
Our great sponsors
Ninject | DryIoc | |
---|---|---|
2 | 1 | |
2,657 | 960 | |
0.1% | - | |
0.0 | 9.5 | |
10 months ago | about 1 month ago | |
C# | C# | |
GNU General Public License v3.0 or later | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Ninject
Posts with mentions or reviews of Ninject.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Is it possible to use both Ninject and Microsoft Dependency injection in a app?
Yes, you can. We use SimpleInjector + our own container abstractions in conjunction with MS one. Also consider reading this - https://github.com/ninject/Ninject/issues/278
-
It do be like that
Then I learned about dependency injection and it suddenly all made perfect sense. I recommend reading this and the following chapter.
DryIoc
Posts with mentions or reviews of DryIoc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-21.
-
Announcing .NET 8 Preview 1
I'd like to keep the convention-based assembly scanning capabilities if ever that was possible. It's too convenient and less error prone than manually registering everything through attributes like current source generator strategies go. DryIocZero supports this somewhat using t4 templates, it gives you a method where you can register your stuff and do assembly scanning and it'll generate your container from there. It works and is quite small and fast but the UX does need some work since t4 is rather clunky to write on.
What are some alternatives?
When comparing Ninject and DryIoc you can also consider the following projects:
Autofac - An addictive .NET IoC container
Unity - This repository contains all relevant information about Unity Container suit
Microsoft.Extensions.DependencyInjection
Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
Castle Windsor - Castle Windsor is a best of breed, mature Inversion of Control container available for .NET
LightInject - An ultra lightweight IoC container
StructureMap - A Dependency Injection/Inversion of Control tool for .NET
TinyIoC - An easy to use, hassle free, Inversion of Control Container for small projects, libraries and beginners alike.
Ninject vs Autofac
DryIoc vs Unity
Ninject vs Microsoft.Extensions.DependencyInjection
DryIoc vs Autofac
Ninject vs Unity
DryIoc vs Microsoft.Extensions.DependencyInjection
Ninject vs Simple Injector
DryIoc vs Simple Injector
Ninject vs Castle Windsor
DryIoc vs LightInject
Ninject vs StructureMap
DryIoc vs TinyIoC