the ninja of .net dependency injectors
C# Batchfile
Pull request Compare This branch is 31 commits behind ninject:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.nuget Update nuget and android pkgs Nov 28, 2014
RemotingServer Changed the InstanceReference to look for interfaces based on type if… Mar 21, 2014
RemotingTestClient Changed the InstanceReference to look for interfaces based on type if… Mar 21, 2014
lib Use Nuget packages instead of lib folder Jul 1, 2013
logos Updated to the latest build scripts Apr 26, 2011
nuget Update Ninject.nuspec Nov 2, 2014
tools Convert to .net 4.5.1, win 8.1; remove sl5 and wp8 Jun 7, 2015
Build-NinjectAndExtensionsWithReleaseTag.bat Added .Net 4.5, SL5 and WP 7.1 builds Jan 10, 2012
LICENSE.txt Updated licensing terms to reflect dual-license with Ms-PL Mar 23, 2009 Removed target which are not supported anymore. Apr 16, 2014
Ninject.include Removed target which are not supported anymore. Apr 16, 2014
Ninject.sln add fa as nuget ref Nov 24, 2015
Ninject.sln.DotSettings Added StyleCop settings file and resharper solution settings file. Apr 24, 2014
Portable.CommonServiceLocator.NinjectAdapter.nuspec Update csl and create release Jul 25, 2014
Portable.Ninject.nuspec Added NuGet only push Nuget and Google code scripts May 23, 2012 Added NuGet only push Nuget and Google code scripts May 23, 2012 Added NuGet only push Nuget and Google code scripts May 23, 2012 Merge branch 'readonlykernel' Jun 6, 2015
appveyor.yml Add AppVeyor config Nov 24, 2015
build.cmd Make it build again using script Jul 25, 2014

Ninject NuGet Version NuGet Downloads

Ninject is a lightning-fast, ultra-lightweight dependency injector for .NET applications. It helps you split your application into a collection of loosely-coupled, highly-cohesive pieces, and then glue them back together in a flexible manner. By using Ninject to support your software's architecture, your code will become easier to write, reuse, test, and modify.

Write your code so it's flexible...

public class Samurai {
    public IWeapon Weapon { get; private set; }
    public Samurai(IWeapon weapon) 
        this.Weapon = weapon;

...and let Ninject glue it together for you.

public class WarriorModule : NinjectModule
    public override void Load() 


  1. Focused. Too many existing dependency injection projects sacrifice usability for features that aren't often necessary. Each time a feature is added to Ninject, its benefit is weighed against the complexity it adds to everyday use. Our goal is to keep the barrier to entry - the baseline level of knowledge required to use Ninject - as low as possible. Ninject has many advanced features, but understanding them is not required to use the basic features.

  2. Sleek. Framework bloat is a major concern for some projects, and as such, all of Ninject's core functionality is in a single assembly with no dependencies outside the .NET base class library. This single assembly's footprint is approximately 85KB when compiled for release.

  3. Fast. Instead of relying on reflection for invocation, Ninject takes advantage of lightweight code generation in the CLR. This can result in a dramatic (8-50x) improvement in performance in many situations.

  4. Precise. Ninject helps developers get things right the first time around. Rather than relying on XML mapping files and string identifiers to wire up components, Ninject provides a robust domain-specific language. This means that Ninject takes advantage of the capabilities of the language (like type-safety) and the IDE (like IntelliSense and code completion).

  5. Agile. Ninject is designed around a component-based architecture, with customization and evolution in mind. Many facets of the system can be augmented or modified to fit the requirements of each project.

  6. Stealthy. Ninject will not invade your code. You can easily isolate the dependency on Ninject to a single assembly in your project.

  7. Powerful. Ninject includes many advanced features. For example, Ninject is the first dependency injector to support contextual binding, in which a different concrete implementation of a service may be injected depending on the context in which it is requested.

Everything else is in Extensions

Yes, sounds slim and focused, but where is the support for all the features that the competitors have?

Generally, they are maintained as specific focused extensions with owners who keep them in sync and pull in new ideas and fixes fast. These are summarized on the extensions section of the project website. Most are hosted alongside the core project right here.


Ninject is intended to be used in both open-source and commercial environments. To allow its use in as many situations as possible, Ninject is dual-licensed. You may choose to use Ninject under either the Apache License, Version 2.0, or the Microsoft Public License (Ms-PL). These licenses are essentially identical, but you are encouraged to evaluate both to determine which best fits your intended use.

Refer to LICENSE.txt for detailed information.

CI build status

Build Status

Changes history