VS MEF
Managed Extensibility Framework (MEF) implementation used by Visual Studio (by microsoft)
Castle Windsor
Castle Windsor is a best of breed, mature Inversion of Control container available for .NET (by castleproject)
Our great sponsors
VS MEF | Castle Windsor | |
---|---|---|
1 | 1 | |
403 | 1,503 | |
2.2% | 0.1% | |
9.3 | 3.6 | |
7 days ago | about 2 months ago | |
C# | 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.
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
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
Castle Windsor
Posts with mentions or reviews of Castle Windsor.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Just saw a new pattern, I call it "almost factory"
Most of the DI containers have a feature of resolving components by name. Here's an example of a "typed factory" that can be provided by the container and the component name can be used to select the service implementation: https://github.com/castleproject/Windsor/blob/master/docs/typed-factory-facility-interface-based.md
What are some alternatives?
When comparing VS MEF and Castle Windsor you can also consider the following projects:
Microsoft.Extensions.DependencyInjection
Autofac - An addictive .NET IoC container
DryIoc - DryIoc is fast, small, full-featured IoC Container for .NET
Ninject - the ninja of .net dependency injectors
Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
Unity - This repository contains all relevant information about Unity Container suit
StructureMap - A Dependency Injection/Inversion of Control tool for .NET
Scrutor - Assembly scanning and decoration extensions for Microsoft.Extensions.DependencyInjection
VS MEF vs Microsoft.Extensions.DependencyInjection
Castle Windsor vs Autofac
VS MEF vs Autofac
Castle Windsor vs Microsoft.Extensions.DependencyInjection
VS MEF vs DryIoc
Castle Windsor vs Ninject
VS MEF vs Simple Injector
Castle Windsor vs Unity
VS MEF vs StructureMap
Castle Windsor vs Simple Injector
VS MEF vs Scrutor
Castle Windsor vs DryIoc