Related Post: http://ihadthisideaonce.com/2012/07/04/from-mef-wtf-to-mef-ftw/
Diagnosing MEF composition failure is tricky, especially when parts have two or more nested dependencies. In this scenario, MEF's error messages aren't very helpful. MEF was unable to satisfy one or more parts in the chain, but the error message points you to the part at the top of the chain, to really fix the problem you need to know about the bottom of the chain. If you start by looking where the error message sends you, you can end up feeling like you're on a wild goose chase because nothing appears to be wrong with that part.
Come to this session to discover tools that can ease your frustration with MEF, and get you out of diagnosis mode and back to coding. I'll show you how to combine these tools with ApprovalTests to create integration tests that provide early warning when something is wrong with your parts. Finally, we'll look at MEF 2 and the diagnostic improvements Microsoft has in store for the next version of this useful extensibility library.