Channel	UnityFx.DependencyInjection
AppVeyor
NuGet
Github

UnityFx.DependencyInjection is a minimalistic lightweight ASP.NET-like dependency injection framework for Unity3d. It provides almost the same API as Microsoft.Extensions.DependencyInjection.Abstractions but supports net35 target, property injection and much simpler implementation.

Features:

• Constructor injection.
• Injection scopes.
• ASP.NET-like minimalistic interface.
• Scopes/loops validation on service initialization (can be disabled).
• Lightweight implementation.
• Unity3d compatibility (net35 target support).

You may need the following software installed in order to build/use the library:

• Microsoft Visual Studio 2017.
• Unity3d.

You can get the code by cloning the github repository using your preffered git client UI or you can do it from command line as follows:

git clone https://github.com/Arvtesh/UnityFx.DependencyInjection.git
git submodule -q update --init

The binaries are available as a NuGet package. See here for instructions on installing a package via nuget. One can also download them directly from Github releases.

As outlined in Wikipedia, dependency injection is a technique whereby one object (or static method) supplies the dependencies of another object. A dependency is an object that can be used (a service). An injection is the passing of a dependency to a dependent object (a client) that would use it. The service is made part of the client's state. Passing the service to the client, rather than allowing a client to build or find the service, is the fundamental requirement of the pattern.

This fundamental requirement means that using values (services) produced within the class from new or static methods is prohibited. The client should accept values passed in from outside. This allows the client to make acquiring dependencies someone else's problem.

The intent behind dependency injection is to decouple objects to the extent that no client code has to be changed simply because an object it depends on needs to be changed to a different one.

Dependency injection is one form of the broader technique of inversion of control. As with other forms of inversion of control, dependency injection supports the dependency inversion principle. The client delegates the responsibility of providing its dependencies to external code (the injector). The client is not allowed to call the injector code; it is the injecting code that constructs the services and calls the client to inject them. This means the client code does not need to know about the injecting code, how to construct the services or even which actual services it is using; the client only needs to know about the intrinsic interfaces of the services because these define how the client may use the services. This separates the responsibilities of use and construction.

Dependency injection involves four roles:

• The service object(s) to be used.
• The client object that depends on the service(s) it uses.
• The interfaces that define how the client may use the services.
• The injector (aka DI container), which is responsible for constructing the services and injecting them into the client.

In constructor injection all client dependencies are provided through a class constructor. Preferred when all dependencies can be constructed first because it can be used to ensure the client object is always in a valid state, as opposed to having some of its dependency references be null (not be set). However, on its own, it lacks the flexibility to have its dependencies changed later. This can be a first step towards making the client immutable and therefore thread safe. In general, this is the recommended approach.

In setter injection the client exposes a setter method (or property) that the injector (DI container) uses for injection of the dependencies. Requires clients to provide a setter method for each dependency. This gives the freedom to manipulate the state of the dependency references at any time. This offers flexibility, but if there is more than one dependency to be injected, it is difficult for the client to ensure that all dependencies are injected before the client could be provided for use.

In interface injection the dependency provides an injector method that will inject the dependency into any client passed to it. Clients must implement an interface that exposes a setter method that accepts the dependency. The advantage of interface injection is that dependencies can be completely ignorant of their clients yet can still receive a reference to a new client and, using it, send a reference-to-self back to the client. In this way, the dependencies become injectors. The key is that the injecting method (which could just be a classic setter method) is provided through an interface.

Reference the DLL (NuGet package) and import the namespace:

using UnityFx.DependencyInjection;

Initialize service descriptors and build a service provider:

var serviceCollection = new ServiceCollection();
serviceCollection.AddSingleton<IMyService>(new MyService());
serviceCollection.AddTransient<IMyService2, MyService2>();
serviceCollection.AddScoped<IMyService3>(sp => new MyService3());
// Add more services here.
var serviceProvider = serviceCollection.BuildServiceProvider();

Note that once service provider is created, there is no way to register new services in it. Now you can use the created service provider to resolve the registered services:

var myService = serviceProvider.GetService<IMyService>();

There are serveral services registered in a service provider by default:

• IServiceProvider
• IServiceScope
• IServiceScopeFactory

Just like in ASP.NET the following service lifetimes supported:

• Transient. Transient lifetime services are created each time they're requested. This lifetime works best for lightweight, stateless services.
• Scoped. Scoped lifetime services are created once per scope (and disposed with the parent scope).
• Singleton. Singleton lifetime services are created the first time they're requested. Every subsequent request uses the same instance. If the app requires singleton behavior, allowing the service container to manage the service's lifetime is recommended.

A new scope can be created using IServiceScopeFactory:

var scope = serviceProvider.GetService<IServiceScopeFactory>().CreateScope();
var scopeServiceProvider = scope.ServiceProvider;

The Dispose method ends the scope lifetime. Once it is called, any scoped services that have been resolved from IServiceProvider will be disposed.

The built-in service container implementation is meant to serve the common needs of the most consumer apps. We recommend using the built-in container unless you need a specific feature that it doesn't support. Some of the features supported in 3rd party containers not found in the built-in container:

• Property/method injection.
• Injection based on name.
• Child containers.
• Custom lifetime management.

Every .NET developer should implement own dependency injection container at least once :). Jokes aside DI has become an industry standard tool for dependency management of any non-trivial application. Unity3d has no built-in DI and all 3rd party container I saw have at least several issues for me:

• They often include much stuff besided DI itself (StrangeIoC).
• While powerful they tend to be quite complex while most applications (well, most of my applications) need just a tiny bit of that (Autofac, Ninject).
• I like ASP.NET approach the most, but the implementation does not support net35 target (still used a lot for Unity) and it still seems too complex for my needs.

That's why I decided to write my own DI framework that provides almost the same API as ASP.NET but much simplier implementation that supports net35 target.

Please see the links below for extended information on the product:

• CHANGELOG.
• SUPPORT.

• Dependency injection.
• Dependency injection in ASP.NET Core.
• Autofac.
• Ninject.
• SimpleInjector.
• StrangeIoC.
• TinyIoC.

Please see contributing guide for details.

The project uses SemVer versioning pattern. For the versions available, see tags in this repository.

Please see the for details.

Working on this project is a great experience. Please see below list of sources of my inspiration (in no particular order):

• ASP.NET source. A great source of knowledge and good programming practices.
• TinyIoC source. The most lightweight IoC container out there.
• Everyone who ever commented or left any feedback on the project. It's always very helpful.