I love it when Glenn and the MEF team make me wrong! Because that means we get something new that I didn’t think they could pull off
First it was Stable Composition.
Now it’s Open Generic Composition.
A closed generic is something like this air code: Public Class x These are the only types of generics I anticipated MEF would support, at least in .NET 4.0. I’ve said this in a number of talks, and I’m happy to say that information is not wrong..
An open generic allows you to expose Foo(Of T) and allow the specific class to be specified by the import.
Note that this is not intrinsic to MEF itself but an alternate catalog. So, it’s not only cool in and of itself that we can now do Open Generics, but it’s a hint at how powerful MEF really is as we move beyond what’s delivered in the box. I’ll let you read Glenn’s post for the details.
What blows me away is that MEF is just starting. I think that’s what amazes me most. It’s like a seed just sprouting, or a kernel we’re just beginning to imagine how to harness. I’m excited about MEF in NET 4.0, but I also think more cool things like this approach to Open Generics will unfold as more people explore MEF.
I’ll follow up with some cool uses I’ve got in mind after I work through the details another day.