MEF as seen on Fig. below, is divided into three main layers Container, Primitives and Attributed Programing Model. Each of these parts is described in Full MEF Architecture here.

• MEF model
• MEF Examples
• MEF Architecture
• More about MEF
• Literature

• Practical section

• Theoretical section
  • Introduction

Theoretical section

1. Introduction

• System.Compostion.* is a lightweight version of MEF, which has been optimized for static composition scenarios and provides faster compositions. It is also the only version of MEF that is as a portable class library and can be used on phone, store, desktop and web applications.

2. MEF model

Roughly speaking, MEF's core is comprised of a catalog and a CompositionContainer?. A catalog is responsible for discovering extensions and the container coordinates creation and satisfies dependencies.

• Parts (i.e. Component) are the cornerstone of MEF. A composable Part offers up one or more Exports, and may also depend on one or more externally provided services or Imports. It is throught this relationship between what a part needs, and what a part can provide that the composition takes place. Service definition is done via Contracts (e.g. an Interface or predefined data type like string).
• Containers perform the actual composition between parts by matching Exports with Imports, that is, service providers with service consumers.
• Catalogs (i.e. Component Repository) are in charge of part discovery. Using different built-in catalogs, an application can find parts within a given assembly or a given folder at runtime. Containers use catalogs to find out which parts they can use during composition.

Longer description here (codeplex wiki).

3. MEF Examples

1. Evil Wizard example - basic usage of MEF.

2. Catalogs example - more Catalog focused

3. Hello World example - External *Codeproject* site!

4. MEF Architecture

Full MEF Architecture described here.

Fig: Different layers in the Managed Extensions Framework.

5. More about MEF

Are you interested to know more about MEF (e.g. "MEF vs standard IoC Container", "MEF Visualizer", "Why to use MEF", "More learing materials" etc.) click here .

6. Literature

• Dependency Injection in .NET
• Programming .NET Components, 2nd Edition
• Pro .NET 1.1 Remoting, Reflection, and Threading

Practical section

Parking lot example writen in C# without using MEF ParkovistePlain. Implementation Attach:ParkingLot_Plain.zip

Parking lot example writen in C# using MEF Dependency Injection ParkovisteMEF. Implementation Attach:ParkingLot_MEF.zip

Theoretical section

1. Introduction

• System.Compostion.* is a lightweight version of MEF, which has been optimized for static composition scenarios and provides faster compositions. It is also the only version of MEF that is as a portable class library and can be

1. Evil Wizard example - basic usage of MEF.

2. Catalogs example - more Catalog focused

3. Hello World example - External *Codeproject* site!

h3. 1. Evil Wizard example - basic usage of MEF.

h3. 2. Catalogs example - more Catalog focused

h3. 3. Hello World example - External *Codeproject* site!

Theoretical section

Practical section

Parking lot example writen in C# without using MEF ParkovistePlain. Implementation Attach:ParkingLot_Plain.zip

Parking lot example writen in C# using MEF Dependency Injection ParkovisteMEF. Implementation Attach:ParkingLot_MEF.zip

Roughly speaking, MEF's core is comprised of a catalog and a CompositionContainer?. A catalog is responsible for discovering extensions and the container coordinates creation and satisfies dependencies.

• Parts (i.e. Component) are the cornerstone of MEF. A composable Part offers up one or more Exports, and may also depend on one or more externally provided services or Imports. It is throught this relationship between what a part needs, and what a part can provide that the composition takes place. Service definition is done via Contracts (e.g. an Interface or predefined data type like string).

• Catalogs (i.e. Component Repository) are in charge of part discovery. Using different built-in catalogs, an application can find parts within a given assembly or a given folder at runtime. Containers use catalogs to find out which parts they can use during composition.

• Catalogs (i.e. Component Repository) are in charge of part discovery. Using different built-in catalogs, an application can find parts within a given assembly or a given folder at runtime. Containers use catalogs to find out which parts they can use during composition.

2. MEF model

Příklad parkoviště napsané v C# s použitím MEF ParkovisteMEF a výsledná implementace Attach:ParkingLot_MEF.zip

Příklad parkoviště napsané v C# bez použití MEF ParkovistePlain a výsledná implementace Attach:ParkingLot_Plain.zip

Praktická část

Příklad parkoviště napsané v C# bez použití MEF ParkovistePlain a výsledná implementace Attach:ParkovistePlain.zip Δ

Příklad parkoviště napsané v C# s použitím MEF ParkovisteMEF a výsledná implementace Attach:ParkovisteMEF.zip Δ

The Managed Extensibility Framework (MEF) is a composition layer for .NET that improves the flexibility, maintainability and testability of large applications. MEF can be used for third-party plugin extensibility, or it can bring the benefits of a loosely-coupled plugin-like architecture to regular applications (MEF support a Plugin Model).

The Managed Extensibility Framework (MEF) is a composition layer for .NET that improves the flexibility, maintainability and testability of large applications. MEF can be used for third-party plugin extensibility, or it can bring the benefits of a loosely-coupled plugin-like architecture to regular applications (MEF support a plugin model).

The Managed Extensibility Framework (MEF) is a composition layer for .NET that improves the flexibility, maintainability and testability of large applications. MEF can be used for third-party plugin extensibility, or it can bring the benefits of a loosely-coupled plugin-like architecture to regular applications (support a plugin model).

• Parts (i.e. Component) are the cornerstone of MEF. Parts known as Exports can provide services to other parts whilst parts known as Imports consume services from other parts. It is throught this relationship between what a part needs, and what a part can provide that the composition takes place. Service definition is done via Contracts (e.g. an Interface or predefined data type like string).

• Parts (i.e. Component) are the cornerstone of MEF. Parts known as Exports can provide services to other parts whilst parts known as Imports consume services from other parts. It is throught this relationship between what a part needs, and what a part can provide that the composition takes place. Service definition is done via Contracts.

• Parts (i.e. component) are the cornerstone of MEF. Parts known as Exports can provide services to other parts whilst parts known as Imports consume services from other parts. It is throught this relationship between what a part needs, and what a part can provide that the composition takes place. Service definition is done via Contracts.

Longer description here (codeplex wiki).

Are you interested to know more about MEF (e.g. "MEF vs standard IoC Container", "MEF Visualizer", "Why to use MEF", "More learing materials" etc.) click here .

Are you interested to know more about MEF (e.g. "MEF vs standard IoC Container", "MEF Visualizer") click here .

Are you interested to know more about MEF (i.e. "MEF vs standard IoC Container", "MEF Visualizer") click here .

Are you interested to know more about "MEF vs standard IoC Container", "MEF Visualizer" click here .

4. MEF Architecture

Full MEF Architecture described here.

The Managed Extensibility Framework (MEF) is a composition layer for .NET that improves the flexibility, maintainability and testability of large applications. MEF can be used for third-party plugin extensibility, or it can bring the benefits of a loosely-coupled plugin-like architecture to regular applications.

• Parts are the cornerstone of MEF. Parts known as Exports can provide services to other parts whilst parts known as Imports consume services from other parts. It is throught this relationship between what a part needs, and what a part can provide that the composition takes place. Service definition is done via Contracts.
• Containers perform the actual composition between parts by matching Exports with Imports, that is, service providers with service consumers.
• Catalogs are in charge of part discovery. Using different built-in catalogs, an application can find parts within a given assembly or a given folder at runtime. Containers use catalogs to find out which parts they can use during composition.

1. Introduction

• System.ComponentModel.Composition.* which has shipped with .NET 4.0 and higher and Silverlight 4. This provides the standard extension model that has been used in Visual Studio.
• System.Compostion.* is a lightweight version of MEF, which has been optimized for static composition scenarios and provides faster compositions. It is also the only version of MEF that is as a portable class library and can be used on phone, store, desktop and web applications.

2. How MEF works

• Parts are the cornerstone of MEF. Parts known as Exports can provide services to other parts whilst parts known as Imports consume services from other parts. It is throught this relationship between what a part needs, and what a part can provide that the composition takes place. Service definition is done via Contracts.
• Containers perform the actual composition between parts by matching Exports with Imports, that is, service providers with service consumers.
• Catalogs are in charge of part discovery. Using different built-in catalogs, an application can find parts within a given assembly or a given folder at runtime. Containers use catalogs to find out which parts they can use during composition.

3. MEF Examples

4. MEF Architecture

5. More about MEF

More

6. Why to use MEF

7. Good explanations

Why to use MEF

10 reasons why to use MEF

3. Hello World example - External *Codeproject* site!

Longer description here (codeplex wiki).

MEF Examples

1. Evil Wizard example - basic usage of MEF.

2. Catalogs example - more Catalog focused

3. Hello World example - External *Codeproject* site!

MEF Example

MEF Architecture

Fig: Different layers in the Managed Extensions Framework.

• Containers comparsion (another Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates and Spring.NET comparsion)

(another Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates and Spring.NET comparsion)

(another comparsion Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates and Spring.NET comparsion)

In-Depth analysis of MEF Architecture

Audio

Code

Video

• Video: MEF Oleg Lvovitch and Kevin Ransom Introduction, MEF 2.0

Presentation

• Presentation: Lecture by Nuno Cancelo
• Presentation: Lecture by Mohamed Meligy

• Spring.NET & Attribute Driven Configuration
• MEF Runtime Plugin Swapping

• Dependency Injection in .NET
• Programming .NET Components, 2nd Edition
• Pro .NET 1.1 Remoting, Reflection, and Threading

There are two versions of MEF:

MEF Architecture

In-Depth analysis of MEF Architecture

http://channel9.msdn.com/posts/NET-45-Oleg-Lvovitch-and-Kevin-Ransom-Managed-Extensibility-Framework-MEF-20 http://www.codeproject.com/Articles/376033/From-Zero-to-Proficient-with-MEF http://www.codeproject.com/Articles/37579/Managed-Extensibility-Framework-Part https://emcpadden.wordpress.com/2008/12/07/managed-extensibility-framework-and-others/

OSGI Spring Links

http://www.javaworld.com/article/2077837/java-se/hello--osgi--part-1--bundles-for-beginners.html http://www.javaworld.com/article/2077853/java-se/hello--osgi--part-2--introduction-to-spring-dynamic-modules.html#resources

In-Depth analysis of MEF Architecture

Another "Hello World!" example

Another "Hello World!" more

• Video: MEF Jan Steberl CZ Introduction MEF - CZ

Longer version here (codeplex wiki).

• Presentation: Lecture by Mohamed Meligy

Nicely writen article about "Mef vs IoC"

Nicely writen article about "Mef vs Ioc" here.

Longer version of this example more.

Longer version of this example .

• Code: Complete MEF Programming Guide

Code: Complete MEF Programming Guide

Its a option to use MEF as a Extension for standard IoC container more.

Interestiong links

Spring.NET & Attribute Driven Configuration MEF Runtime Plugin Swapping

Hosting MEF Extensions in an IoC Container

• Presentation: Lecture by Nuno Cancelo

• Interception (another example Interception using Dependency Injection Container)

• Interception another example Interception using Dependency Injection Container

• Interception

• Code: Glenn Block - Building Composable Apps in .NET 4 with the Managed Extensibility Framework Complete explanations of MEF capabilities

The Managed Extensibility Framework (MEF) is a composition layer for .NET that improves the flexibility, maintainability and testability of large applications. MEF can be used for third-party plugin extensibility, or it can bring the benefits of a loosely-coupled plugin-like architecture to regular applications.

The Managed Extensibility Framework (MEF) is a composition layer for .NET that improves the flexibility, maintainability and testability of large applications. MEF can be used for third-party plugin extensibility, or it can bring the benefits of a loosely-coupled plugin-like architecture to regular applications.

• Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates and Spring.NET comparsion

• Containers comparsion
• Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates, Spring.NET,
• OSGi.net

.NET IoC/DI options:

Containers comparsion

Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates, Spring.NET,

 OSGi.net

.NET IoC/DI options: Containers comparsion

• Code as Configuration
• Auto Registration
• XML configuration
• Custom Lifetimes
• Interception

• Per graph
• Web Request Context
• Thread Context
• Session Context
• Pooled
• Scoped
• Custom Reference

• 1. Code as Configuration
• 2. Auto Registration
• 3. XML configuration
• 4. Custom Lifetimes
• 5. Interception

• 1. Per graph
• 2. Web Request Context
• 3. Thread Context
• 4. Session Context
• 5. Pooled
• 6. Scoped
• 7. Custom Reference

MEF vs standard IoC Container

.NET IoC/DI options:

Unity, Castle Windsor, Ninject facilitates, Spring.NET, OSGi.net Containers comparsion

There are two versions of MEF:

10 reasons why to use MEF

10 reason why to use MEF

.NET IoC/DI options:

• Audio: MEF with Glenn Block IoC, DI vs MEF

• Audio: MEF with Glenn Block IoC, DI vs MEF

• Video: MEF Oleg Lvovitch and Kevin Ransom Introduction, MEF 2.0

• Audio: MEF with Glenn Block
• Code: Barbarian Meets MEF
• Video: MEF Oleg Lvovitch and Kevin Ransom

Video: MEF Oleg Lvovitch and Kevin Ransom

Code: Barbarian Meets MEF

MEF Example

Another .NET IoC/DI options:

Good explanations

Audio: MEF with Glenn Block

How MEF works

How it works

• Parts are the cornerstone of MEF. Parts known as Exports can provide services to other parts whilst parts known as Imports consume services from other parts. It is throught this relationship between what a part needs, and what a part can provide that the composition takes place. Service definition is done via Contracts.
• Containers perform the actual composition between parts by matching Exports with Imports, that is, service providers with service consumers.
• Catalogs are in charge of part discovery. Using different built-in catalogs, an application can find parts within a given assembly or a given folder at runtime. Containers use catalogs to find out which parts they can use during composition.

Helps to see what is going on inside the MEF Composition Container. Download

Download

=csharp ApplicationContext ctx = new ClassPathXmlApplicationContext("cz/zcu/kiv/project/beanDefinition.xml");

=java122[=

[=

Container = new CompositionContainer?(

                new AggregateCatalog?(
                    new AssemblyCatalog?( Assembly.GetExecutingAssembly?() ) ,
                    new AssemblyCatalog?( Assembly.LoadFrom?( @"MEFVisualizer?.Exe" ) )
                    ) );

            Container.Compose( batch );

            var meftoDgml = new MEFToDGML?( Container){ IsNamespaceGrouping? = true };   // The Visualizer

           meftoDgml.WriteToDGMLFile?();   // Write to DGML file

Container = new CompositionContainer(
new AggregateCatalog(
new AssemblyCatalog( Assembly.GetExecutingAssembly() ) ,
new AssemblyCatalog( Assembly.LoadFrom( @"MEFVisualizer.Exe" ) )
) );

Container.Compose( batch );

var meftoDgml = new MEFToDGML( Container){ IsNamespaceGrouping = true };   // The Visualizer

meftoDgml.WriteToDGMLFile();   // Write to DGML file

Helps to see what is going on inside the MEF Composition Container

Attach:MEF_Visualization

Attach:MEFVisualisation.png Δ

http://wiki.kiv.zcu.cz/uploads/UvodDoKomponent/MEF_Visualization

MEF Visualizer

MEF Visualization

• System.Compostion.* is a lightweight version of MEF, which has been optimized for static composition scenarios and provides faster compositions. It is also the only version of MEF that is as a portable class library and can be used on phone, store, desktop and web applications.

System.Compostion. is a lightweight version of MEF, which has been optimized for static composition scenarios and provides faster compositions. It is also the only version of MEF that is as a portable class library and can be used on phone, store, desktop and web applications.

DI is based on three dimensions, Object Composition, Lifetime Management, and Interception.

Literature

TODO

TODO

Introduction

MEF vs IoC Container

Another .NET options: Unity Castle Windsor Ninject facilitates Spring.NET

MEF vs IoC Container

Literature

Dependency Injection in .NET

Barbarian Meets MEF

Interception using Dependency Injection Container

 DI is based on three dimensions, Object Composition, Lifetime Management, and Interception.

Dependency Injection in .NET

MEF has potential, but as a DI container, it lacks:

1. Code as Configuration 2. Auto Registration 3. XML configuration (not so important to me) 4. Custom Lifetimes 5. Interception Those things are pretty important.

For Lifestyle it lacks:

1. Per graph 2. Web Request Context 3. Thread Context 4. Session Context 5. Pooled 6. Scoped 7. Custom Reference

Unity, Castle Windsor, Ninject facilitates, Spring.NET

Spring.NET

• http://channel9.msdn.com/Blogs/JanSteberl/Managed-Extensibility-Framework

• http://www.slideshare.net/Mohamed_Meligy/managed-extensibility-framework-mef

Introduction

MEF Programming Guide

Hosting MEF Extensions in an IoC Container

In-Depth analysis of MEF Architecture

Introduction

Lecture

• System.ComponentModel?.Composition.* which has shipped with .NET 4.0 and higher and Silverlight 4. This provides the standard extension model that has been used in Visual Studio.

http://www.slideshare.net/NunoCancelo/give-more-life-to-your-application-extending-it-with-mef

MEF Runtime Plugin Swapping

• System.ComponentModel?.Composition.* which has shipped with .NET 4.0 and higher and Silverlight 4. This provides the standard extension model that has been used in Visual Studio.

Introduciton The Managed Extensibility Framework (MEF) is a composition layer for .NET that improves the flexibility, maintainability and testability of large applications. MEF can be used for third-party plugin extensibility, or it can bring the benefits of a loosely-coupled plugin-like architecture to regular applications.

• System.ComponentModel?.Composition.* which has shipped with .NET 4.0 and higher and Silverlight 4. This provides the standard extension model that has been used in Visual Studio.
• System.Compostion.*_ is a lightweight version of MEF, which has been optimized for static composition scenarios and provides faster compositions. It is also the only version of MEF that is as a portable class library and can be used on phone, store, desktop and web applications.

• http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework
• http://mef.codeplex.com/wikipage?title=Overview&referringTitle=Home
• http://www.mstv.cz/vyvojari/videos/239/Managed-Extensibility-Framework
• http://stackoverflow.com/questions/15572302/difference-between-mef-and-ioc-containers-likeunity-autofac-smap-ninject-windso
• http://stackoverflow.com/questions/709532/is-mef-osgi-for-net
• https://mef.codeplex.com/discussions/209827
• http://www.hanselman.com/blog/HanselminutesPodcast148MEFManagedExtensibilityFrameworkWithGlennBlock.aspx
• http://stackoverflow.com/questions/216565/why-exactly-isnt-mef-a-di-ioc-container
• http://stackoverflow.com/questions/108116/mef-managed-extensibility-framework-vs-ioc-di
• http://msdn.microsoft.com/en-us/magazine/gg650670.aspx
• http://the-tread-way.blogspot.cz/2010/04/springnet-attribute-driven.html
• http://www.slideshare.net/Mohamed_Meligy/managed-extensibility-framework-mef
• http://channel9.msdn.com/Shows/10-4/10-4-Episode-26-Creating-Extensible-Applications-with-the-Managed-Extensibility-Framework

• http://mef.codeplex.com
• http://www.codeproject.com/Articles/188054/An-Introduction-to-Managed-Extensibility-Framework

http://www.codeproject.com/Articles/188054/An-Introduction-to-Managed-Extensibility-Framework

TODO http://mef.codeplex.com