Have a question?
AutoDI is both a dependency injection container and a framework to simplify working with dependency injection (DI). It is built on top of the Microsoft.Extensions.DependencyInjection.Abstractions library, and it works very similar to the way ASP.NET Core handles dependency injection.
AutoDI delivers delivers two excellent features:
- It expands the Microsoft.Extensions.DependencyInjection.Abstractions library to bring the same type of dependency injection to other platforms (.NET Framework, WPF, Xamarin, UWP, etc).
- It generates container registrations at compile time using conventions (of course you can also add on more at run-time as well).
See the wiki for more details or check out the Quick Start page to get up and running fast.
The goal of this library is to make dependency injection as simple as adding a Nuget package.
In addition to standard constructor dependency injection, it also allows you to simply declare optional constructor parameters that will be resolved any time the constructor is invoked.
In a typical DI setup, you can often find your objects needing to take in dependencies that the object is not actually using, but needs them to pass into some other object. The bigger and deeper the object model gets, the worse this becomes.
As a specific example, imagine you are inside of class Foo and wish to create an instance of Bar, but Bar has a dependency on IService.
In many cases, one of several options can be used:
- Pass a facade to either the DI container or a factory that can create a
Bar - Add a dependency on
Footo take in anIServiceso that when it needs to create aBarit can simply pass the instance in.
Though both these options work, they add additional effort. After all, in most cases when we want a Bar we simply call new Bar();. AutoDI lets you write exactly that, and moves the dependency resolution inside of Bar's constructor.
This dependency resolution is then forwarded to your favorite DI container to resolve it.
AutoDI.Container aims to take this one step further: rather than needing to rely on a third-party DI container at run-time, it will generate one at compile-time. In addition to being fast, this saves you the hassle of setting up and maintaining configuration code for your DI container.
Probably. Take a look at the AutoDI.Examples repository for samples. There are examples of adding support for other DI containers as well as simple examples for most frameworks.
Don't see your favorite listed? I accept PRs.
Needle designed by Austin Andrews from Material Design Icons