.NET 4.0 MEF FAQ (Socket, Plug, and extension)

Introduction and Goal

This FAQ deep dives into .Net 4.0 MEF fundamentals (Import and Export) and also explains when to use MEF over DI / IOC. This article also explains step by step how to use MEF in various technologies like Silverlight, WPF, and ASP.NET.
Please feel free to download by free .NET Ebook which has 400 questions and answers in WCF, WPF, WWF, Silverlight, and a lot more from here. View our 300 videos Design Patter, UML, Function Points, Enterprises Application Block, WCF, WPF, WWF, LINQ, SQL Server, Silverlight, .NET Project, SDLC, OOP's, .NET Best Practices, ASP.NET 4.0 From here

What is MEF (Manage extensibility framework)?

MEF is a framework by which you can make your application extensible. For example, you have an accounting application and you would like to provide a hook (socket) where external vendors can connect (plug) and add invoicing capabilities to the accounting application.
For instance, you have an application in which you would want different vendors to connect with their features and extend your application.
So the vendors just put the components in the application, the application discovers them, and does the connection and extension.
1.jpg

How can we implement MEF in .NET 4.0?

Implementing MEF is a three-step process:-
2.jpg

Can we see a simple example of MEF with the above 3 steps?

We will create a simple class which will have a hook to import string message. In other words, any class that has the functionality of string message implementation can attach itself to the hook and extend that class.
Step 1:- Create the socket (Import)
 The first step is to create a place holder/hook/socket where other components can plugin.
Import the below namespaces needed by MEF.
  1. using System.ComponentModel.Composition;
  2. using System.ComponentModel.Composition.Hosting;
  3. using System.Reflection;
To define a hook we have created an empty property called as "ImportMessage" and we have attributed the same with "Import" attribute.
  1. class Program {
  2. [Import()]
  3. public string ImportMessage {
  4. set;
  5. get;
  6. }
  7. }
The above "import" attribute says that anyone who has a string functionality implementation type can connect to me and attach the functionality.
Step 2:- Create and attach the plug (Export)
In order to create the plug or extension we need to use the "Export" attribute as shown below. This attribute in the current scenario does nothing but displays a simple string.
  1. class clsMySimpleMessage {
  2. [Export()]
  3. string ExportMessage {
  4. set {}
  5. get {
  6. return "Message inserted via MEF";
  7. }
  8. }
  9. }
Step 3: Connect and Extend it (Compose it)
 Ok so we have created the socket, the plug and it's time to connect these both. Below goes the code for the same.
  1. private void Compose() {
  2. // Get a reference to the current assemblies in the project.
  3. AssemblyCatalog catalog = new AssemblyCatalog(Assembly.GetExecutingAssembly()); // Once you have got the reference of catalog add it to the composition container.
  4. CompositionContainer compositionContainer = new CompositionContainer(catalog); // Finally call composeparts to connect the Import with Export.
  5. compositionContainer.ComposeParts(this); // use the property
  6. Console.WriteLine(ImportMessage);
  7. Console.ReadLine();
  8. }
In other words export, import and compose, Below figure summarizes the same.
3.jpg
"Export" is like things you give off and "import" is like things which you take in.

Should data types of import and export match?

The types of import and export should match or else while composing you will get an error as shown below. Can incompatible socket and plug connect?.
4.jpg
5.jpg

Can we connect import and export via some defined contract rather than .NET data types?

In the real world your hooks would be some real-world contract types like a customer, supplier, etc rather than simple .NET data types like string, int, Boolean, etc. In order to create a real word kind of hook in MEF, we need to first create a contract using interfaces as shown below.
  1. interface ImyInterface {
  2. string getString();
  3. }
We need to ensure that the hooks defined in both import and export attributes are of the same interface type as shown below. The binding logic using the composition container does not change; it's the same as described in the previous section.

This looks very much similar to DI and IOC, why the re-invention?

  1. [Export(typeof(ImyInterface))]
  2. class clsMyImplementation: ImyInterface
  3. {
  4. public string getString()
  5. {
  6. return "This is my string";
  7. }
  8. }
  10. class Program
  11. {
  12. [Import()]
  13. public ImyInterface myInterface
  14. {
  15. set;
  16. get;
  17. }
  18. }
In case you are new to DI/IOC read from here
Both of them overlap each other to a very great extent but the GOALS are different. DI and IOC is meant for decoupling while MEF is for extensibility. The below requirement will throw more light on how to decide which solution to go for:-
Requirement Solution
The application should be a tiered application with each tier decoupled from the other for better reusability and maintainability. DI IOC
The application should provide a facility for exporting data into different formats. External vendors should be able to plug in their own export mechanism into the application. MEF
Below table summarizes the same in a detailed manner.
DI / IOC MEF
Decoupling Yes
Extensibility Yes
Integrate Known things Yes
Integrate Unknown thing Yes
Automatic discovery Yes
Registration Yes
Discovery Yes
Compile-time Yes
Run time Yes
If you have still questions post it to Glenn Block over here http://codebetter.com/blogs/glenn.block/archive/2009/08/16/should-i-use-mef-for-my-general-ioc-needs.aspx

Can they work hand in hand?

Let say you have an application and the following is your requirement.
Requirement Solution
The application should be 3 tier architecture with UI, BO, and DAL layers decoupled from each other. DI IOC
The data access layer needs to be open and extensible. The application will provide the ability to vendors to plug their own data connection mechanism so that the application can connect to their proprietary databases. MEF
The way to approach the first requirement is by using your favorite IOC container and the second requirement is where MEF fits. The below diagram shows how they fit into the whole game.
The end GOAL is more important when making a choice between them.
6.jpg
Below is a nice article by Mr. Nicholas Blumhardt which shows how MEF and IOC fit in.
http://blogs.msdn.com/b/nblumhardt/archive/2009/03/16/hosting-mef-extensions-in-an-ioc-container.aspx

We would like to see a sample in Silverlight?

The main important steps do not change.
Step 1:- Create the socket (Import)
Define the Silverlight items you want to import. In the below code snippet we have defined a collection of user control type.
  1. public partial class MainPage: UserControl {
  2. [ImportMany]
  3. public ObservableCollection < UserControl > ImportedItems { get;
  4. set; }
  5. }
Step 2:- Create and attach the plug (Export)
Use "Export" to define the plug. For the current scenario, we have defined two Silverlight user control with export attributes exposing "UserControl" as the type.
  1. [Export(typeof(UserControl))]
  2. public partial class SilverlightControl1: UserControl
  3. {
  4. public SilverlightControl1()
  5. {
  6. InitializeComponent();
  7. }
  8. }
  9. [Export(typeof(UserControl))]
  10. public partial class SilverlightControl2: UserControl
  11. {
  12. public SilverlightControl2()
  13. {
  14. InitializeComponent();
  15. }
  16. }
Step 3: Connect and Extend it (Compose it)
 Use the "SatisfyImport" to compose the exports and imports.
  1. CompositionInitializer.SatisfyImports(this);
If you run the same you should see the composed user controls in the main Silverlight UI container as shown below.
7.jpg
The whole Silverlight picture looks something as shown below.
8.jpg

Can we also see a simple Sample in WPF?

Phrrr..phusss….tired will update soon.

How about some Samples in ASP.NET?

Phrrr..phusss….tired will update soon.

Source code

You can get the source code attached with this article from the top of this article.

Reference