VS MEF VS DryIoc

Compare VS MEF vs DryIoc and see what are their differences.

VS MEF

Managed Extensibility Framework (MEF) implementation used by Visual Studio (by microsoft)
IoC Mef Visual Studio Extensibility extensibility-engine
Source Code
Suggest alternative
Edit details

DryIoc

DryIoc is fast, small, full-featured IoC Container for .NET (by dadhi)
IoC Dryioc di-ioc-container Dependency Injection inversion-of-control Netstandard Xamarin Netcore Performance Simplicity Prism
Source Code
Suggest alternative
Edit details
InfluxDB
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors
VS MEF DryIoc
1 1
403 963
2.2% -
9.3 9.5
7 days ago about 1 month ago
C# C#
MIT License 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.

VS MEF

Posts with mentions or reviews of VS MEF. We have used some of these posts to build our list of alternatives and similar projects.
  • .NET Core plugin system
    1 project | /r/csharp | 1 Oct 2022
    This is good info! I had not heard of MEF being split up like this. Looks like there's a full explanation of everything here: https://github.com/microsoft/vs-mef/blob/main/doc/mef_library_differences.md

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 VS MEF and DryIoc you can also consider the following projects:

Microsoft.Extensions.DependencyInjection

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

Autofac - An addictive .NET IoC container

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

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

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

Ninject - the ninja of .net dependency injectors

Scrutor - Assembly scanning and decoration extensions for Microsoft.Extensions.DependencyInjection

LightInject - An ultra lightweight IoC container

VS MEF vs Microsoft.Extensions.DependencyInjection DryIoc vs Unity VS MEF vs Autofac DryIoc vs Autofac VS MEF vs Simple Injector DryIoc vs Microsoft.Extensions.DependencyInjection VS MEF vs Castle Windsor DryIoc vs Simple Injector VS MEF vs StructureMap DryIoc vs Ninject VS MEF vs Scrutor DryIoc vs LightInject