I can't seem to find any articles or links to how to do this and it seems like an obvious problem (eg when you don't have the source code or want to use existing types not written for MEF in mind)
If you're looking to add an existing object instance to your container, you can use the CompositionContainer.ComposeExportedValue
method:
container.ComposeExportedValue<MyClass>(myClassInstance);
The thing you're really looking for though is probably the new convention-based programming model, which allows you to create parts based on naming conventions rather than attributes, but this feature is only available in .NET 4.5.
Usage example (this will export every type in myAssembly
which implements IController
as an IController
):
var registration = new RegistrationBuilder();
registration.ForTypesDerivedFrom<IController>()
.Export<IController>();
var catalog = new AssemblyCatalog(myAssembly, registration);
var container = new CompositionContainer(catalog);
A good example of how to use MEF's new convention model can be found here.
Hope this helps.
If you mark an interface with the InheritedExport attribute, all modules within the catalog are exported, which implement this interface, whether they are marked with an Export attribute or not.
Interface:
[InheritedExport]
public interface IContract { ... }
Module:
// No [Export] attribute
public class ModuleImplementation : IContract { ... }
Now MEF will inject the module.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With