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 [[MEFarchitecture | here]].

** [[UvodDoKomponent.MEF#model| MEF model]]
** [[UvodDoKomponent.MEF#example| MEF Examples]]
** [[UvodDoKomponent.MEF#architecture| MEF Architecture]]
** [[UvodDoKomponent.MEF#more| More about MEF]]
** [[UvodDoKomponent.MEF#literature| Literature]]
* [[UvodDoKomponent.MEF#practical | Practical section]]

* [[UvodDoKomponent.MEF#theoretical | Theoretical section]]
** [[UvodDoKomponent.MEF#intro| Introduction]]

-> 1. [[MEFWizardExample | Evil Wizard example ]] - basic usage of MEF.
-> 2. [[MEFExample | Catalogs example ]] - more *Catalog* focused
-> 3. [[Hello World example-> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]] - [@ External *Codeproject* site! @]

h1. [[#theoretical]] Theoretical section

h2. [[#intro]] 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.

h2. [[#model]] 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.

-> %width=500px%Attach:mef.png

----> Longer description [[here -> http://mef.codeplex.com/wikipage?title=Overview&referringTitle=Home]] (codeplex wiki).

h2. [[#example]] 3. MEF Examples

--> 1. [[MEFWizardExample | Evil Wizard example ]] - basic usage of MEF.
--> 2. [[MEFExample | Catalogs example ]] - more *Catalog* focused
--> 3. [[Hello World example-> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]] - [@ External *Codeproject* site! @]

h2. [[#architecture]] 4. MEF Architecture

Full MEF Architecture described [[MEFarchitecture | here]].
-> Attach:arch1_thumb.png
---> *Fig*: _Different layers in the Managed Extensions Framework._


h2. [[#more]] 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 [[MEFmore | here]] .

h2. [[#literature]] 6. Literature
*[[Dependency Injection in .NET -> http://www.amazon.com/Dependency-Injection-NET-Mark-Seemann/dp/1935182501]]
*[[Programming .NET Components, 2nd Edition -> http://www.amazon.com/Programming-NET-Components-Juval-Lowy/dp/0596102070/]]
*[[Pro .NET 1.1 Remoting, Reflection, and Threading -> http://www.amazon.com/Pro-NET-Remoting-Reflection-Threading/dp/1590594525/]]


h1. [[#practical]] 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

h1. [[#proc]] Theoretical section

h2. 1. [[#Introduction]] 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. [[MEFWizardExample | Evil Wizard example ]] - basic usage of MEF.
--> 2. [[MEFExample | Catalogs example ]] - more *Catalog* focused
--> 3. [[Hello World example-> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]] - [@ External *Codeproject* site! @]

-> !!! 1. [[MEFWizardExample | Evil Wizard example ]] - basic usage of MEF.

-> h3. 1. [[MEFWizardExample | Evil Wizard example ]] - basic usage of MEF.
-> h3. 2. [[MEFExample | Catalogs example ]] - more *Catalog* focused
-> h3. 3. [[Hello World example-> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]] - [@ External *Codeproject* site! @]

--> h3. 1. [[MEFWizardExample | Evil Wizard example ]] - basic usage of MEF.
--> h3. 2. [[MEFExample | Catalogs example ]] - more *Catalog* focused
--> h3. 3. [[Hello World example-> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]] - [@ External *Codeproject* site! @]

h1. Theoretical section

h1. 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.

h2. 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

h1. 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 -> https://www.google.cz/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CCMQFjAA&url=http%3A%2F%2Fmsdn.microsoft.com%2Fcs-cz%2Flibrary%2Fdd460648%2528v%3Dvs.110%2529.aspx&ei=QgGgVN6XFMz7aPadgYgO&usg=AFQjCNF8DQdQojB0Aslm3_ImIUcjaS-n8w&sig2=rxSYq3UH2K8kdjt26fMAxw&bvm=bv.82001339,d.d2s ]]) 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 -> https://www.google.cz/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CCMQFjAA&url=http%3A%2F%2Fmsdn.microsoft.com%2Fcs-cz%2Flibrary%2Fdd460648%2528v%3Dvs.110%2529.aspx&ei=QgGgVN6XFMz7aPadgYgO&usg=AFQjCNF8DQdQojB0Aslm3_ImIUcjaS-n8w&sig2=rxSYq3UH2K8kdjt26fMAxw&bvm=bv.82001339,d.d2s ]]) 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 -> https://www.google.cz/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CCMQFjAA&url=http%3A%2F%2Fmsdn.microsoft.com%2Fcs-cz%2Flibrary%2Fdd460648%2528v%3Dvs.110%2529.aspx&ei=QgGgVN6XFMz7aPadgYgO&usg=AFQjCNF8DQdQojB0Aslm3_ImIUcjaS-n8w&sig2=rxSYq3UH2K8kdjt26fMAxw&bvm=bv.82001339,d.d2s ]]) 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 -> http://mef.codeplex.com/wikipage?title=Overview&referringTitle=Home]] (codeplex wiki).

-> %width=500px%Attach:mef.png

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 [[MEFmore | here]] .

-> Attach:arch1_thumb.png
---> *Fig*: _Different layers in the Managed Extensions Framework._

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

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

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

-> Attach:mef.png

------> Longer description [[here -> http://mef.codeplex.com/wikipage?title=Overview&referringTitle=Home]] (codeplex wiki).

h2. 4. MEF Architecture

Full MEF Architecture described [[MEFarchitecture | here]].

The *Managed Extensibility Framework* ([[MEF -> https://www.google.cz/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CCMQFjAA&url=http%3A%2F%2Fmsdn.microsoft.com%2Fcs-cz%2Flibrary%2Fdd460648%2528v%3Dvs.110%2529.aspx&ei=QgGgVN6XFMz7aPadgYgO&usg=AFQjCNF8DQdQojB0Aslm3_ImIUcjaS-n8w&sig2=rxSYq3UH2K8kdjt26fMAxw&bvm=bv.82001339,d.d2s ]]) 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.

h2. 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.

h2. 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.

h2. 3. MEF Examples

h2. 4. MEF [[MEFarchitecture | Architecture]]

h2. 5. More about MEF
[[MEFmore | More]]

h2. 6. Why to use MEF

h2. 7. Good explanations

h2. Why to use MEF

[[10 reasons why to use MEF -> http://csharperimage.jeremylikness.com/2010/04/ten-reasons-to-use-managed.html]]

h3. 3. [[Hello World example-> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]] - [@ External *Codeproject* site! @]

Longer description [[here -> http://mef.codeplex.com/wikipage?title=Overview&referringTitle=Home]] (codeplex wiki).

h2. MEF Examples

h3. 1. [[MEFWizardExample | Evil Wizard example ]] - basic usage of MEF.
h3. 2. [[MEFExample | Catalogs example ]] - more *Catalog* focused
h3. 3. Hello World [[example-> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]] - [@ External *Codeproject* site! @]

h2. MEF [[MEFExample | Example]]

h2. MEF [[MEFarchitecture | Architecture]]
Attach:arch1_thumb.png
*Fig*: _Different layers in the Managed Extensions Framework._

*[[Containers comparsion-> http://featuretests.apphb.com/DependencyInjection.html]] (another [[Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates and Spring.NET comparsion -> http://elegantcode.com/2009/01/07/ioc-libraries-compared/]])

(another [[Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates and Spring.NET comparsion -> http://elegantcode.com/2009/01/07/ioc-libraries-compared/]])

(another comparsion [[Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates and Spring.NET comparsion -> http://elegantcode.com/2009/01/07/ioc-libraries-compared/]])

[[In-Depth analysis of MEF Architecture -> https://kishore1021.wordpress.com/window-8-winrt/in-depth-analysis-of-mef-architecture/]]

h3. Audio

h3. Code

h3. Video
*[[Video: MEF Oleg Lvovitch and Kevin Ransom -> http://channel9.msdn.com/posts/NET-45-Oleg-Lvovitch-and-Kevin-Ransom-Managed-Extensibility-Framework-MEF-20]] Introduction, MEF 2.0

h3. Presentation
*[[Presentation: Lecture by Nuno Cancelo -> http://www.slideshare.net/NunoCancelo/give-more-life-to-your-application-extending-it-with-mef]]
*[[Presentation: Lecture by Mohamed Meligy -> http://www.slideshare.net/Mohamed_Meligy/managed-extensibility-framework-mef]]

*[[Spring.NET & Attribute Driven Configuration -> http://the-tread-way.blogspot.cz/2010/04/springnet-attribute-driven.html]]
*[[MEF Runtime Plugin Swapping -> http://paxcel.net/blog/mef-runtime-plugin-swapping/]]

*[[Dependency Injection in .NET -> http://www.amazon.com/Dependency-Injection-NET-Mark-Seemann/dp/1935182501]]
*[[Programming .NET Components, 2nd Edition -> http://www.amazon.com/Programming-NET-Components-Juval-Lowy/dp/0596102070/]]
*[[Pro .NET 1.1 Remoting, Reflection, and Threading -> http://www.amazon.com/Pro-NET-Remoting-Reflection-Threading/dp/1590594525/]]

h3.There are two versions of MEF:

h2. MEF Architecture

[[In-Depth analysis of MEF Architecture -> https://kishore1021.wordpress.com/window-8-winrt/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/

h2. 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 -> https://kishore1021.wordpress.com/window-8-winrt/in-depth-analysis-of-mef-architecture/]]

Another "Hello World!" [[example-> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]]

Another "Hello World!" [[more -> http://www.codeproject.com/Articles/56635/Managed-Extensibility-Framework]]

*

*[[Video: MEF Jan Steberl CZ -> http://channel9.msdn.com/Blogs/JanSteberl/Managed-Extensibility-Framework]] Introduction MEF - CZ

Attach:mef.png
Longer version [[here -> http://mef.codeplex.com/wikipage?title=Overview&referringTitle=Home]] (codeplex wiki).

*[[Presentation: Lecture by Mohamed Meligy -> http://www.slideshare.net/Mohamed_Meligy/managed-extensibility-framework-mef]]

Nicely writen article about "Mef vs IoC"

Nicely writen article about "Mef vs Ioc"
[[here -> http://msdn.microsoft.com/en-us/magazine/gg650670.aspx]].

*

Longer version of this example [[more -> http://www.codeproject.com/Articles/188054/An-Introduction-to-Managed-Extensibility-Framework]].

Longer version of this example [[more -> * http://www.codeproject.com/Articles/188054/An-Introduction-to-Managed-Extensibility-Framework]].

*[[Code: Complete MEF Programming Guide -> https://mef.codeplex.com/wikipage?title=Guide&referringTitle=Overview]]

[[Code: Complete MEF Programming Guide -> https://mef.codeplex.com/wikipage?title=Guide&referringTitle=Overview]]

Its a option to use MEF as a Extension for standard IoC container [[more -> http://blogs.msdn.com/b/nblumhardt/archive/2009/03/16/hosting-mef-extensions-in-an-ioc-container.aspx]].

h2. Interestiong links
[[Spring.NET & Attribute Driven Configuration -> http://the-tread-way.blogspot.cz/2010/04/springnet-attribute-driven.html]]
[[MEF Runtime Plugin Swapping -> http://paxcel.net/blog/mef-runtime-plugin-swapping/]]

[[Hosting MEF Extensions in an IoC Container -> http://blogs.msdn.com/b/nblumhardt/archive/2009/03/16/hosting-mef-extensions-in-an-ioc-container.aspx]]

*[[Presentation: Lecture by Nuno Cancelo -> http://www.slideshare.net/NunoCancelo/give-more-life-to-your-application-extending-it-with-mef]]

*[[Interception -> http://msdn.microsoft.com/en-us/magazine/gg535676.aspx]] (another example [[Interception using Dependency Injection Container -> http://www.freeportmetrics.com/blog/interception-using-dependency-injection-container-unity-to-achieve-separation-of-concerns/]])

*[[Interception -> http://msdn.microsoft.com/en-us/magazine/gg535676.aspx]] another example [[Interception using Dependency Injection Container -> http://www.freeportmetrics.com/blog/interception-using-dependency-injection-container-unity-to-achieve-separation-of-concerns/]]

*[[Interception -> http://msdn.microsoft.com/en-us/magazine/gg535676.aspx]]

*[[Code: Glenn Block - Building Composable Apps in .NET 4 with the Managed Extensibility Framework -> http://msdn.microsoft.com/en-us/magazine/ee291628.aspx]] Complete explanations of MEF capabilities

The Managed Extensibility Framework ([[MEF -> https://www.google.cz/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CCMQFjAA&url=http%3A%2F%2Fmsdn.microsoft.com%2Fcs-cz%2Flibrary%2Fdd460648%2528v%3Dvs.110%2529.aspx&ei=QgGgVN6XFMz7aPadgYgO&usg=AFQjCNF8DQdQojB0Aslm3_ImIUcjaS-n8w&sig2=rxSYq3UH2K8kdjt26fMAxw&bvm=bv.82001339,d.d2s ]]) 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 -> http://msdn.microsoft.com/cs-cz/library/dd460648(v=vs.110).aspx ]]) 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 -> http://elegantcode.com/2009/01/07/ioc-libraries-compared/]]

*[[Containers comparsion-> http://featuretests.apphb.com/DependencyInjection.html]]
*[[Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates, Spring.NET, -> http://elegantcode.com/2009/01/07/ioc-libraries-compared/]]
*[[OSGi.net -> http://osgi.codeplex.com]]

h3. .NET IoC/DI options:
[[Containers comparsion-> http://featuretests.apphb.com/DependencyInjection.html]]

[[Unity, StructurMap, Autofac, Castle Windsor, Ninject facilitates, Spring.NET, -> http://elegantcode.com/2009/01/07/ioc-libraries-compared/]]
[[OSGi.net -> http://osgi.codeplex.com]]

h3. .NET IoC/DI options: [[Containers comparsion-> http://featuretests.apphb.com/DependencyInjection.html]]

*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

h2. MEF vs standard IoC Container

h3. .NET IoC/DI options:
Unity, Castle Windsor, Ninject facilitates, Spring.NET, [[OSGi.net -> http://osgi.codeplex.com]]
[[Containers comparsion-> http://featuretests.apphb.com/DependencyInjection.html]]

*There are two versions of MEF:*

[[10 reasons why to use MEF -> http://csharperimage.jeremylikness.com/2010/04/ten-reasons-to-use-managed.html]]

[[10 reason why to use MEF -> http://csharperimage.jeremylikness.com/2010/04/ten-reasons-to-use-managed.html]]

.NET IoC/DI options:

*[[Audio: MEF with Glenn Block -> http://www.hanselminutes.com/148/mef-managed-extensibility-framework-with-glenn-block]] [@IoC@], DI vs MEF

*[[Audio: MEF with Glenn Block -> http://www.hanselminutes.com/148/mef-managed-extensibility-framework-with-glenn-block]] IoC, DI vs MEF

*[[Video: MEF Oleg Lvovitch and Kevin Ransom -> http://channel9.msdn.com/posts/NET-45-Oleg-Lvovitch-and-Kevin-Ransom-Managed-Extensibility-Framework-MEF-20]] Introduction, MEF 2.0

*[[Audio: MEF with Glenn Block -> http://www.hanselminutes.com/148/mef-managed-extensibility-framework-with-glenn-block]]
*[[Code: Barbarian Meets MEF -> http://www.barbarianmeetscoding.com/blog/2012/08/14/barbarian-meets-mef-managed-extensiblity-framework/]]
*[[Video: MEF Oleg Lvovitch and Kevin Ransom -> http://channel9.msdn.com/posts/NET-45-Oleg-Lvovitch-and-Kevin-Ransom-Managed-Extensibility-Framework-MEF-20]]

[[Video: MEF Oleg Lvovitch and Kevin Ransom -> http://channel9.msdn.com/posts/NET-45-Oleg-Lvovitch-and-Kevin-Ransom-Managed-Extensibility-Framework-MEF-20]]

[[Code: Barbarian Meets MEF -> http://www.barbarianmeetscoding.com/blog/2012/08/14/barbarian-meets-mef-managed-extensiblity-framework/]]

h2. MEF Example

Another .NET IoC/DI options:

h2. Good explanations
[[Audio: MEF with Glenn Block -> http://www.hanselminutes.com/148/mef-managed-extensibility-framework-with-glenn-block]]

h2. How MEF works
Attach:mef.png

h2. 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 -> http://mefvisualizer.codeplex.com]]

[[Download -> http://mefvisualizer.codeplex.com]]

%width=700px%Attach:MEF_Visualization.png

->[@
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
@]

(:source lang=css header="$HTMLStylesFmt['sourceblock'] = '" footer="';":)
[=
.sourceblocklink {
text-align: right;
font-size: smaller;
}
.sourceblocktext {
padding: 0.5em;
border: 1px solid #808080;
color: #000000;
background-color: #F1F0ED;
}
.sourceblocktext div {
font-family: monospace;
font-size: small;
line-height: 1;
height: 1%;
}

.sourceblocktext div.head,
.sourceblocktext div.foot {
font: italic medium serif;
padding: 0.5em;
}=]

=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

(:code:) [=

(:code=csharp:) [=
// C# source code goes here
=]

=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
=]

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

Attach:MEF_Visualization.png

Attach:MEF_Visualization

Attach:MEF_Visualization.png

Attach:komp-subkomp.png

Attach:MEFVisualisation.png

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

(:attachlist:)

h2. MEF Visualizer
Attach:MEF_Visualization.png

h2. 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.

h2. Literature

h2. TODO

h1. TODO

h2. Introduction

h2. MEF vs IoC Container

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

h1. MEF vs IoC Container

h1. Literature
[[Dependency Injection in .NET -> http://www.amazon.com/Dependency-Injection-NET-Mark-Seemann/dp/1935182501]]

[[Barbarian Meets MEF -> http://www.barbarianmeetscoding.com/blog/2012/08/14/barbarian-meets-mef-managed-extensiblity-framework/]]

[[Interception using Dependency Injection Container -> http://www.freeportmetrics.com/blog/interception-using-dependency-injection-container-unity-to-achieve-separation-of-concerns/]]

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

[[Dependency Injection in .NET -> http://www.amazon.com/Dependency-Injection-NET-Mark-Seemann/dp/1935182501]]

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://the-tread-way.blogspot.cz/2010/04/springnet-attribute-driven.html]]

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

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

h1. Introduction

[[MEF Programming Guide -> https://mef.codeplex.com/wikipage?title=Guide&referringTitle=Overview]]

[[Hosting MEF Extensions in an IoC Container -> http://blogs.msdn.com/b/nblumhardt/archive/2009/03/16/hosting-mef-extensions-in-an-ioc-container.aspx]]

[[In-Depth analysis of MEF Architecture -> https://kishore1021.wordpress.com/window-8-winrt/in-depth-analysis-of-mef-architecture/]]

Introduction

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

*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 -> http://paxcel.net/blog/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