Input via Mark Smith:
6) Now that MEF is in the framework, it would be nice to connect some of this all up with MEF - instead of having a static list of algorithms, parsers, formatters, etc. that is not extendable by the end-user who is writing their own, adding an InheritedExport attribute onto the interfaces would allow you to ImportMany on those static classes and see 3rd party classes automatically. It's a fantastic way to inject dependencies automatically.
- MBF already has custom registration module, where the new algos, parsers, formatters and etc., can be added from add-in DLLs (using interface). Do we need to move to MEF?