Comments on: Exploring MEF Extensibility Points

By: Building a Configuration Binder for MEF with POCO Support | Sidar Ok Technical Blog !

Mon, 14 Jul 2008 02:34:50 +0000

[…] About Sidar Sidar Ok Technical Blog ! « Exploring MEF Extensibility Points […]

By: Sidar Ok

Sidar Ok — Mon, 07 Jul 2008 23:19:32 +0000

Hi Krysztof, thanks and it is a relief to hear that the documentation will get better

I will be constantly watching the deliveries, thanks again!

By: Krzysztof Cwalina

Krzysztof Cwalina — Mon, 07 Jul 2008 21:51:03 +0000

Sidar,

This is a great post! Really nice you got so far with the very limited documentation that we shipped in the first CTP. It will get better overtime.

BTW, we are now in the middle of a milestone where we invested very heavily in the MEF extensibility model (which we call “primitives”). Once we ship an update to the CTP, I would be really interested in your feedback on how you compare the CTP #1 extensibility API to the new design.

By: Jason Olson

Jason Olson — Fri, 04 Jul 2008 22:08:08 +0000

Hello again Sidar. As mentioned in our private correspondence, my post on creating a Fluent Interface for MEF is now up on my blog: http://www.managed-world.com/2008/07/04/BuildingAFluentInterfaceForMEF.aspx.

Enjoy!

By: Sidar Ok

Sidar Ok — Fri, 04 Jul 2008 22:04:54 +0000

Hi Jason, thanks for pointing that out. Looking forward to your post about it.

By: Jason Olson

Jason Olson — Fri, 04 Jul 2008 18:48:48 +0000

You actually can use customer resolvers. There is an overload to the CompositionContainer constructor that accepts a ValueResolver parameter.

With this overload, you can have a custom Resolver that itself will going through and all the custom Binders (so a consumer of your custom classes never need to add binders directly).

I’ll have a sample going up on my blog today that shows how to use these extension points to build a fluent interface for registration/retrieval of dependencies, without having to use attributes whatsoever.