The error indicates that it can't find an export of type IFolderViewExtension. Note that this is different from the import of IFolderItemsViewExtension you have shown.
The error indicates that it can't find an export of type IFolderViewExtension. Note that this is different from the import of IFolderItemsViewExtension you have shown. My guess is that the problem is not that you have multiple IFolderItemsViewExtensions, but that you have multiple IFolderViewExtensions, or there is some other contract that you have more than one of that you are using with an import that requires exactly one.
This may be caused because you have the same assembly in more than one of your directory catalogs. It is easy for this to happen if you have a reference to an assembly and copy local is set to true.
1 Daniel's probably spot on here; don't forget that there are aster ways to debug MEF problems than trial-and-error. You should probably dump composition state as described here mef.codeplex. Com/… – Nicholas Blumhardt Dec 28 '09 at 22:13 Thanks for the help.
I started removing the Imports from the controls that were themselves exports and everything works. I put the Imports back in and now I'm unable to reproduce the original problem to begin with. Bottom-line though...it works now.
Thanks Daniel and Nicholas. I'm just now getting my feet week on MEF and am very blown-away by it's power and potential for fully extensible applications on the desktop. – user120985 Dec 29 '09 at 3:19.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.