MEF CTP 1 Released

re: MEF CTP 1 Released

Vagif Abilov — Fri, 06 Jun 2008 07:09:50 GMT

Krzysztof,

Can you emphasize what are the principle differences between MEF and Unity DI framework from Enterprise Library? AFAIK Unity also supports attribute-based dependency setup.

Managed Extensibility Framework CTP 공개

bkchung's WebLog — Fri, 06 Jun 2008 10:52:51 GMT

Krzysztof Cwalina  MEF CTP 1 Released (소식) Managed Extensibility Framework – Home (메인페이지) Managed

re: MEF CTP 1 Released

Martin Bohring — Fri, 06 Jun 2008 11:50:32 GMT

Hello Krzysztof,

it is nice to see those efforts from Microsoft.

But something is not very clear for me.

How is the relation between MEF and MAF ? How does the Unity application block from P&P fit into this new landscape ?

Please feel the pain of all the SW architects trying to base their new architectures onto somethings that is future proof.

This really becomes more difficult from day to day.

I don't mean to bash onto those projects, but a bit more coordinated efforts would be much appreciated.

How is the big picture and design rational of all those somehow releated sub frameworks

MEF: Microsoft's Managed Extensibility Framework

Kirill Osenkov — Sat, 07 Jun 2008 22:45:03 GMT

Krzysztof Cwalina announced that Microsoft has released a CTP of its Managed Extensibility Framework

Managed Extensibility Framework CTP1

Matthieu MEZIL — Sun, 08 Jun 2008 10:35:07 GMT

Krzysztof Cwalina a annoncé la première CTP public de Managed Extensibility Framework (MEF) . Pour faire

Managed Extensibility Framework CTP1

Matthieu MEZIL — Sun, 08 Jun 2008 10:43:08 GMT

Krzysztof Cwalina announced first public Managed Extensibility Framework (MEF) CTP . What's this

Aktualizováno: Managed Extensibility Framework

Minority blog — Wed, 11 Jun 2008 21:53:59 GMT

public class HelloWorld { [Import] // import declares what a component needs public OutputDevice Output;

re: MEF CTP 1 Released

Björn Rochel — Sun, 20 Jul 2008 13:22:25 GMT

Hey Kzysztof.

when I first read your first blog entry about MEF (http://blogs.msdn.com/kcwalina/archive/2008/04/25/MEF.aspx) and your example at the end of it I was actually a bit confused, too.

Seeing a container and some bootstrapping at application startup reminded me of a lot of samples I've seend from different IoC - containers. Reading more and more comments to that post my confusion even grew. I was asking myself: "Why are they building yet another IoC container?"

However, after downloading the CTP and reading though the code I guess (at least for me) the example shown in the blog entry was a bit misleading.

We are talking about dynamic application extensibillity, right? Dynamic in the sense of dynamic discoverabillity and dynamic binding which seem to be core aspects of MEF (as least as I interpret it). If so, an example only showing bootstrapping at application startup is confusing because it reminds most people of a plain old IoC-container.

From what I've seen so far MEF and IoC-containers serve a completly different purpose. MEF is not trying to be an IoC-container or an application composition framework. It's primary purpose is to enable easy third party extensibillity and integration. Dependency Injection is only an implementation aspect of MEF, not the purpose of the framework.

That beeing said I very much liked the Calculator example in the CTP because it demonstrates quite well, how MEF could be beneficial in real world scenarios.

On the feature side I would be very happy if the team could realize constructor injection for extensions.

To conclude this : I really appreciate what your team is trying to achive and I am looking forward to extensibillity features in the next .NET-Framework . . .