Pure.DI.Templates 2.1.58

Supports .NET starting with .NET Framework 2.0, released 2005-10-27, and all newer versions.

Usage requirements

Usage Requirements

• .NET SDK 6.0.4+
  Required for compilation. Projects can target older frameworks (e.g., .NET Framework 2.0).
• C# 8+
  Only required for projects using the Pure.DI source generator. Other projects support any C# version.

Key Features

Pure.DI is a compile-time dependency injection (DI) code generator that replaces runtime containers with lightweight, well-optimized code.

✔️ No Containers, Zero Overhead

Pure.DI is actually a .NET code generator. It uses basic language constructs to create simple code as well as if you were doing it yourself: de facto it's just a bunch of nested constructor calls. This code can be viewed, analyzed at any time, and debugged.

✔️ Compile-Time Validation

All logic for analyzing the graph of objects, constructors and methods takes place at compile time. Pure.DI notifies the developer at compile time of missing or cyclic dependencies, cases when some dependencies are not suitable for injection, etc. The developer has no chance to get a program that will crash at runtime because of some exception related to incorrect object graph construction. All this magic happens at the same time as the code is written, so you have instant feedback between the fact that you have made changes to your code and the fact that your code is already tested and ready to use.

✔️ Zero Dependencies

No external libraries.

✔️ Native Performance

• Compiler/JIT Optimized: Matches hand-written code efficiency.
• Minimal Memory: Allocates only necessary objects. No boxing, delegates, or dynamic calls.

✔️ Works everywhere

Since the pure DI approach does not use any dependencies or .NET reflection at runtime, it does not prevent the code from running as expected on any platform: Full .NET Framework 2.0+, .NET Core, .NET, UWP/XBOX, .NET IoT, Xamarin, Native AOT, etc.

✔️ Familiar Syntax

The Pure.DI API is very similar to the API of most IoC/DI libraries. And this was a conscious decision: the main reason is that programmers don't need to learn a new API.

✔️ Precise Generics

In Pure.DI it is proposed to use special marker types instead of using open generic types. This allows you to build the object graph more accurately and take full advantage of generic types.

✔️ Built-in BCL Support

Pure.DI already supports many of BCL types like Array, IEnumerable<T>, IList<T>, IReadOnlyCollection<T>, IReadOnlyList<T>, ISet<T>, IProducerConsumerCollection<T>, ConcurrentBag<T>, Func<T>, ThreadLocal, ValueTask<T>, Task<T>, MemoryPool<T>, ArrayPool<T>, ReadOnlyMemory<T>, Memory<T>, ReadOnlySpan<T>, Span<T>, IComparer<T>, IEqualityComparer<T> and etc. without any extra effort.

✔️ Ideal for Libraries

Its high performance, zero memory consumption/preparation overhead, and lack of dependencies make it ideal for building libraries and frameworks.

NuGet packages