Microsoft.Extensions.DependencyInjection VS DryIoc

Compare Microsoft.Extensions.DependencyInjection vs DryIoc and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
Microsoft.Extensions.DependencyInjection DryIoc
0 1
859 960
- -
0.0 9.5
- 7 days ago
C# C#
- MIT License
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.

Microsoft.Extensions.DependencyInjection

Posts with mentions or reviews of Microsoft.Extensions.DependencyInjection. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning Microsoft.Extensions.DependencyInjection yet.
Tracking mentions began in Dec 2020.

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
    2 projects | /r/dotnet | 21 Feb 2023
    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.

What are some alternatives?

When comparing Microsoft.Extensions.DependencyInjection and DryIoc you can also consider the following projects:

Autofac - An addictive .NET IoC container

Unity - This repository contains all relevant information about Unity Container suit

Ninject - the ninja of .net dependency injectors

Castle Windsor - Castle Windsor is a best of breed, mature Inversion of Control container available for .NET

Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.

Lamar - Fast Inversion of Control Tool and Successor to StructureMap

VS MEF - Managed Extensibility Framework (MEF) implementation used by Visual Studio

StructureMap - A Dependency Injection/Inversion of Control tool for .NET

TinyIoC - An easy to use, hassle free, Inversion of Control Container for small projects, libraries and beginners alike.