here's my problem: I have a bunch of parts discovered by MEF using both a directorycatalog and an assemblycatalog with the current executing directory. It works all fine and dandy on my computer, but when I send my work to others, it only composes the parts
in the assemblycatalog.
Now here's what I've checked: I've used the diagnostics DLL included with mefx.exe to dump out a diagnostic log to a file, but on said persons computer, this log only contains information on the parts found in the assembly catalog.
I've also checked after calling ComposeParts that the assemblies that I *want* to compose are indeed found by the directorycatalog. No composition exception is thrown, just a silent failure to compose, and I can't reproduce this problem on my home computer.
I've also checked that the metadata wasn't causing the issue (both by removing the importation of it, and weakly typing it)
What's weirder is that it used to compose them before for others, but now it does not. It seems pretty hit or miss, with it working for some, but not working for others.
I'm using .NET4, WPF4, and VS2010 all RC1. My compile options are for Any CPU targetting the .NET4 Client Profile. Is there anything i'm missing? Anything which would cause MEF to silently fail to satisfy my imports?