This article needs additional citations for verification .(June 2022) |
![]() | |
Developer(s) | Microsoft |
---|---|
Stable release | V1 in .NET Framework 4.0 / April 12, 2010 |
Preview release | V2 Preview 5 / December 19, 2011 |
Repository | github |
Written in | .NET Languages |
Operating system | Windows |
Platform | .NET Framework |
Type | Web application framework |
License | MIT License [1] |
Website | docs |
Managed Extensibility Framework (MEF) is a component of .NET Framework 4.0 aiming to create lightweight, extensible applications. It aims to allow .NET application developers to discover and use extensions with no configuration required. It also aims to let extension developers encapsulate code easily and avoid fragile hard dependencies. Furthermore, it aims to allow extensions to be reused across applications. [2] MEF was introduced as a part of .NET 4.0 [3] and Silverlight 4. It was later improved with the release of .NET 4.5 by adding support for generic types and the introduction of a convention-based extension model. [4]
MEF aims to solve the runtime extensibility problem. Without MEF, any application that wants to support a plugin model needs to create its own infrastructure from scratch. Those plugins will often be application-specific and cannot be reused across multiple implementations.
Roughly speaking, MEF's core consists of a catalog and a CompositionContainer. A catalog is responsible for discovering extensions and the container coordinates creation and satisfies dependencies.