DryIoc
DryIoc is fast, small, full-featured IoC Container for .NET (by dadhi)
Unity
This repository contains all relevant information about Unity Container suit (by unitycontainer)
Our great sponsors
| DryIoc | Unity | |
|---|---|---|
| 1 | 2 | |
| 960 | 1,642 | |
| - | 0.3% | |
| 9.5 | 0.0 | |
| 29 days ago | 3 months ago | |
| C# | ||
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DryIoc
Posts with mentions or reviews of DryIoc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-21.
-
Announcing .NET 8 Preview 1
I'd like to keep the convention-based assembly scanning capabilities if ever that was possible. It's too convenient and less error prone than manually registering everything through attributes like current source generator strategies go. DryIocZero supports this somewhat using t4 templates, it gives you a method where you can register your stuff and do assembly scanning and it'll generate your container from there. It works and is quite small and fast but the UX does need some work since t4 is rather clunky to write on.
Unity
Posts with mentions or reviews of Unity.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-01.
-
Godot moves from SFConservancy to a new, dedicated Godot Foundation!
What I would say about this is that it rarely happens successfully. The reality is that usually no one outside the main maintainers of an OSS project can be bothered / is capable of continuing the project. I often see massive OSS projects run by 1 to a few people, when they want to move on and ask the community to take over there is crickets. A recent example I've seen is the Unity dependency injector. So many people were using it and just 0 real interest in someone actually taking it over.
-
WPF Prism devs, which container do you use?
Autofac is mentioned here https://github.com/unitycontainer/unity/discussions/368
What are some alternatives?
When comparing DryIoc and Unity you can also consider the following projects:
Autofac - An addictive .NET IoC container
Microsoft.Extensions.DependencyInjection
Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
Ninject - the ninja of .net dependency injectors
LightInject - An ultra lightweight IoC container
Castle Windsor - Castle Windsor is a best of breed, mature Inversion of Control container available for .NET
TinyIoC - An easy to use, hassle free, Inversion of Control Container for small projects, libraries and beginners alike.
StructureMap - A Dependency Injection/Inversion of Control tool for .NET
DryIoc vs Autofac
Unity vs Autofac
DryIoc vs Microsoft.Extensions.DependencyInjection
Unity vs Microsoft.Extensions.DependencyInjection
DryIoc vs Simple Injector
Unity vs Ninject
DryIoc vs Ninject
Unity vs Simple Injector
DryIoc vs LightInject
Unity vs Castle Windsor
DryIoc vs TinyIoC
Unity vs StructureMap