A while ago I said it couldn’t be done, at least without hacky string parsing. Folks weren’t happy and they let us know it including Oren. Our team know the power that open-generic support brings to systems, but at the time there was no clean way to implement it in MEF.
Recently I had the pleasure of having a nice lively discussion on Herding Code with my cohorts Ward Bell, Rob Eisenberg and Jeremy Miller around one of our favorite topics, Presentation Patterns. We let the gloves come off and went at it for about 2 hours.
Disclaimer: This is not an encouragement to use MEF to replace your IoC container, these are guidelines to help those who are considering it’s use.
This has been a question we hear again and again both internally and externally. MEF in V1 is targetting third-party extensibility scenarios,
<Warning>Long post follows</Warning>
Lately there is a lot of momentum and interesting conversation around Model-View-View-Model. There’s several good resources out there that discuss the basics of the pattern, who the actors are that are involved and what role the play. I’ll let those speak for themselves,
Nick just posted on a new and very important feature we added in Preview 6 which we call Stable Composition. To give you an idea of why we added this, in the past if you had a part, say OrderProcessor, that had a required import of ILogger, and no logger was present, then composition would fail, and in so doing would corrupt the state of the container.