Managed Extensibility Framework
This article needs additional citations for verification. (June 2022) |
| Managed Extensibility Framework | |
|---|---|
![]() | |
| Developer | Microsoft |
| Stable release | V1 in .NET Framework 4.0
/ April 12, 2010 |
| Preview release | V2 Preview 5
/ December 19, 2011 |
| Written in | C# |
| Operating system | Windows |
| Platform | .NET Framework |
| Type | Web application framework |
| License | MIT License[1] |
| Website | docs |
| Repository | github |
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]
Overview
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.
- MEF aims to provide a standard way for the host application to expose itself and consume external extensions. Extensions, by their nature, could be reused amongst different applications. However, an extension can still be implemented in a way that is application-specific. Extensions themselves can depend on one another and MEF aims to make sure they are wired together in the correct order, sparing the developer from doing it manually.
- MEF offers a set of discovery approaches for the application to locate and load available extensions.
- MEF allows tagging extensions with additional metadata which aims to facilitate rich querying and filtering.
Design
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.
- MEF's first-class citizen is the ComposablePart class. A composable part offers up one or more Exports, and may also depend on one or more externally provided services or Imports. A composable part also manages an instance, which can be an object instance of a given type (it is in the default MEF implementation)[clarification needed]. MEF, however, is extensible and additional ComposablePart implementations can be provided as long as they adhere to the Import/Export contracts.
- Exports and imports each have a Contract. Contracts are the bridge between exports and imports. An export contract can consist of further metadata that can be used to filter on its discovery. For example, it might indicate a specific capability that the export offers.
- MEF's container interacts with Catalogs to have access to composable parts. The container itself resolves a part's dependencies and exposes Exports to the outside world. Composable part instances may be added directly to the container.
- A ComposablePart returned by a catalog will likely be an extension to the application. It might have Imports (dependencies) on components the host application offers, and it's likely to Export others.
- The default MEF composable part implementation uses attribute-based metadata to declare exports and imports. This allows MEF to determine which parts, imports, and exports are available through discovery.
References
- ^ "MEF". GitHub. 15 October 2021.
- ^ Kanjilal, Joydip (7 July 2016). "How to work with the Managed Extensibility Framework in C#". InfoWorld. Retrieved 25 June 2022.
- ^ Pronschinske, Mitch (12 April 2010). "What's New in VS2010 and .Net 4?". DZone. Retrieved 25 June 2022.
- ^ Vogel, Eric (12 February 2010). "Managed Extensibility Framework Improvements in .NET 4.5". VisualStudio Magazine. Retrieved 25 June 2022.
Further reading
- Likness, Jeremy (2011). Fundamentals of the Managed Extensibility Framework (MEF). Addison-Wesley. ISBN 978-0132929400.
- Verma, Rishabh (2020). Visual Studio Extensibility Development: Extending Visual Studio IDE for Productivity, Quality, Tooling, and Analysis. Apress. ISBN 978-1484258538.
- Harris, Alan (2010). Pro ASP.NET 4 CMS: Advanced Techniques for C# Developers Using the .NET 4 Framework. Apress. ISBN 978-1430227137.
- Nagel, Christian; Evjen, Bill; Glynn, Jay; Watson, Karli; Skinner, Morgan (2010). Professional C# 4.0 and .NET 4. John Wiley & Sons. ISBN 978-0470632536.
External links
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.
