Ninject
the ninja of .net dependency injectors (by ninject)
Castle Windsor
Castle Windsor is a best of breed, mature Inversion of Control container available for .NET (by castleproject)
Our great sponsors
| Ninject | Castle Windsor | |
|---|---|---|
| 2 | 1 | |
| 2,655 | 1,502 | |
| 0.1% | 0.1% | |
| 0.0 | 3.6 | |
| 10 months ago | about 1 month ago | |
| C# | C# | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
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.
Castle Windsor
Posts with mentions or reviews of Castle Windsor.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Just saw a new pattern, I call it "almost factory"
Most of the DI containers have a feature of resolving components by name. Here's an example of a "typed factory" that can be provided by the container and the component name can be used to select the service implementation: https://github.com/castleproject/Windsor/blob/master/docs/typed-factory-facility-interface-based.md
What are some alternatives?
When comparing Ninject and Castle Windsor you can also consider the following projects:
Autofac - An addictive .NET IoC container
Microsoft.Extensions.DependencyInjection
Unity - This repository contains all relevant information about Unity Container suit
Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
DryIoc - DryIoc is fast, small, full-featured IoC Container for .NET
StructureMap - A Dependency Injection/Inversion of Control tool for .NET
Scrutor - Assembly scanning and decoration extensions for Microsoft.Extensions.DependencyInjection
Ninject vs Autofac
Castle Windsor vs Autofac
Ninject vs Microsoft.Extensions.DependencyInjection
Castle Windsor vs Microsoft.Extensions.DependencyInjection
Ninject vs Unity
Castle Windsor vs Unity
Ninject vs Simple Injector
Castle Windsor vs Simple Injector
Ninject vs DryIoc
Castle Windsor vs DryIoc
Ninject vs StructureMap
Castle Windsor vs Scrutor