Steven
Steven
Simple Injector currently locks on a very fine grained level, and often pushes the problem of locking to sub parts of the library and to anyone who extends the library....
Simple Injector tries to detect as much as possible at registration time. In case multiple generic types are registered for the same abstraction, Simple Injector will throw directly at the...
Batch registration sometimes requires to call the `GetTypesToRegister` method, which can be a hassle and this method is hard to find. Instead of using `GetTypesToRegister` this could be integrated in...
All `Register` overloads of the registration API return `void`. By instead returning an object that describes the made registration, it would allow users and third parties to build extension methods...
Simple Injector allows its dependency injection behavior to be altered by the use of the `IDependencyInjectionBehavior` interface, e.g.: ``` c# var container = new Container(); container.Options.DependencyInjectionBehavior = new CustomBehavior(container); ```...
When dealing with types that mix primitive types and dependencies in their constructor, there are currently three ways to deal with this; they are: - Register a delegate that creates...
The use of a DI container comes with a certain increase of memory pressure. This happens because the container must be informed about all registrations and their metadata. This metadata...
`Analyzer.Analyze` returns, beside diagnostic warnings, [diagnostic info messages](https://simpleinjector.readthedocs.io/en/latest/diagnostics.html#supported-information-messages) as well. It can be useful to add an additional info message that notes the case where a conditional registration is never...
Added a new project for Simple Injector with the appropriate assembly references and NuGet package. To be able to succeed I had to add an IsDecorated overload to the AspectUtility,...