How to use MEF architecture for plugin design?

MEF provides Declarative, attribute based programming model.


MEF journey starts by adding the reference to the following assembly

System.ComponentModel.Composition

MEF solves the problem of extensibility (Adding or replacing functionality without modification to the system.)

Example:
We can replace default wheel of a car by the provided extension point.

Hi developers/Engineers/Architects,

More than 400 views but ZERO reply.

OK. no problem. I try myself to answer this question.

I got some understanding with MEF architecture. Please add your share to make solid understanding.


The .NET 4 Framework offers two technologies for writing flexible application that load add-ins dynamically. One technology is the Managed Extensibility Framework (MEF) and the another technology that has been available since .NET 3.5 is the Managed Add-in Framework (MAF).

MAF uses a pipeline for communication between the add-in and the host application that makes the development process more complex but also offers separation of add-ins via appdomains or even different process. In that regard, MEF is the simpler of the two technologies.

MEF is built up with parts and containers. A container finds parts from a catalog. The catalog finds parts within an assembly or a directory. The container connects imports to exports and, thus, make parts available to the hosting application.

Thanks,

Mursaleen Fayyaz

Junior Software Engineer