MEF on Mono doesn't work properly?

Answer 1

So I'm assuming that the exports are defined in external assemblies, because you use the DirectoryPartCatalog.. either there is an issue with the file path handling in the catalog or the problem is in the AttributedAssemblyPartCatalog / AttributedTypesPartCatalog

Internally the DirectoryPartCatalog wraps each discovered assembly into an AttributedAssemblyPartCatalog which in turn uses a AttributedTypesPartCatalog

Your best bet is to add the MEF project into your solution, instead of the dll, and set a break point in the greediest constructors of DirectoryPartCatalog & AttributedAssemblyPartCatalog and step until u find the problem

Unfortunatly I do not have a mono machine setup so I can't help more than that

Answer 2

Adding the interface and the two implementations to the application assembly works. So I'll have debug like you suggested, need to find a decent debugger for mono though.

Answer 3

With the latest MEF release (Preview 4 - http://www.codeplex.com/MEF) it works just fine!

Since the bug is no longer relevant I voted to close this question.