To get a high level overview of Simple Injector, please visit our website or dive directly into our documentation. And did you know there's a Simple Injector blog?
The goal of Simple Injector is to provide .NET application developers with an easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
Many of the existing DI libraries have a big complicated legacy API or are new, immature, and lack features often required by large scale development projects. Simple Injector fills this gap by supplying a simple implementation with a carefully selected, but complete set of features that allow you to write highly maintainable applications. Features like decorator registration and container-verification set it apart from the other containers. In the end, you will realize that there only two types of DI Containers—Simple Injector... and the rest.
The following platforms are supported:
- .NET 4.0 and up.
- .NET Standard including:
- Universal Windows Programs.
- Mono.
- .NET Core.
- Xamarin.
Simple Injector is carefully designed to run in partial / medium trust, and it is fast; blazingly fast.
The easiest way to get started is by installing the available NuGet packages. Take a look at the Using section in the documentation on learning how to configure and use Simple Injector. Go to the Integration page to find out how to integrate Simple Injector in your favorate application framework. Look at the More Information section to learn more or if you have any questions.
The general idea behind Simple Injector (or any DI library for that matter) is that you design your application around loosely coupled components using the dependency injection pattern while adhering to the Dependency Inversion Principle. Take for instance the following UserController class in the context of an ASP.NET MVC application:
Note: Simple Injector works for many different technologies and not just MVC. Please see the integration for help using Simple Injector with your technology of choice.
public class UserController : Controller
{
private readonly IUserRepository repository;
private readonly ILogger logger;
// Use constructor injection for the dependencies
public UserController(IUserRepository repository, ILogger logger)
{
this.repository = repository;
this.logger = logger;
}
// implement UserController methods here:
public ActionResult Index()
{
this.logger.Log("Index called");
return View(this.repository.GetAll());
}
}
public class SqlUserRepository : IUserRepository
{
private readonly ILogger logger;
// Use constructor injection for the dependencies
public SqlUserRepository(ILogger logger)
{
this.logger = logger;
}
public User GetById(Guid id)
{
this.logger.Log("Getting User " + id);
// retrieve from db.
}
}The UserController class depends on the IUserRepository and ILogger interfaces. By not depending on concrete implementations, you can test UserController in isolation. But ease of testing is only one of a number of things that Dependency Injection gives you. It also enables you, for example, to design highly flexible systems that can be completely composed in one specific location (often the startup path) of the application.
Using Simple Injector, the configuration of the application using the UserController and SqlUserRepository classes shown above, might look something like this:
protected void Application_Start(object sender, EventArgs e)
{
// 1. Create a new Simple Injector container
var container = new Container();
// 2. Configure the container (register)
container.Register<IUserRepository, SqlUserRepository>(Lifestyle.Transient);
container.Register<ILogger, MailLogger>(Lifestyle.Singleton);
container.Register<UserController>();
// 3. Optionally verify the container's configuration.
container.Verify();
// 4. Register the container as MVC3 IDependencyResolver.
DependencyResolver.SetResolver(new SimpleInjectorDependencyResolver(container));
}Tip: If you start with a MVC application, take a look at the ASP.NET MVC integration guide.
The given configuration registers implementations for the IUserRepository and ILogger interfaces. The code snippet shows a few interesting things. First of all, you can map concrete instances (such as SqlUserRepository) to an interface or base type. In the given example, every time you ask the container for an IUserRepository, it will always create a new SqlUserRepository on your behalf (in DI terminology: an object with a Transient lifestyle).
The seconds registration maps the ILogger interface to a MailLogger implementation. This MailLogger is registered with the Singleton lifestyle—only one instance of MailLogger will ever be created by the Container.
Using this configuration, when a UserController is requested, the following object graph is constructed:
new UserController(
new SqlUserRepository(
logger),
logger);Note that object graphs can become very deep. What you can see is that not only UserController contains dependencies, so does SqlUserRepository. In this case SqlUserRepository itself contains an ILogger dependency. Simple Injector will not only resolve the dependencies of UserController but will instead build a whole tree structure of any level deep for you.
And this is all it takes to start using Simple Injector. Design your classes around the SOLID principles and the Dependency Injection pattern (which is actually the hard part) and configure them during application initialization. Some frameworks (such as ASP.NET MVC) will do the rest for you, other frameworks (like ASP.NET Web Forms) will need a little bit more work. See the integration guide for examples of many common application frameworks.
Please go to the using section in the documentation to see more examples.
For more information about Simple Injector please visit the following links:
- using will guide you through the Simple Injector basics.
- The Object Lifetime Management page explains how to configure lifestyles such as transient, singleton, and others.
- See the Reference library for the complete API documentation of the latest version.
- See the integration guide for more information about how to integrate Simple Injector into your specific application framework.
- For more information about Dependency Injection in general, please visit this page on Stackoverflow.
- If you have any questions about how to use Simple Injector or about dependency injection in general, the experts at Stackoverflow.com are waiting for you.
- For all other Simple Injector related question and discussions, such as bug reports and feature requests, the Simple Injector discussion forum will be the place to start.
- The book Dependency Injection Principles, Practices, and Patterns presents core DI patterns in plain C# so you’ll fully understand how DI works.
Happy injecting!