Jul 29, 2010 at 3:38 PM
Edited Jul 29, 2010 at 4:46 PM
first of all, thanks for this great piece of work even if it's very complex for a beginner.
I've just started to play around with the quickstarts and experience several problems with the modularity samples. For some reason i'm not able to add own modules to either RemoteModularityQuickstart or DefiningModulesInCodeQuickStart (my teammate tried
different sample but with no success too).
Here is, what i've done with RemoteModularityQucikStart:
I made a copy of ModuleX and renamed everything to ModuleA, added a new ModuleInfoGroup to ModuleCatalog.xaml (just copied / renamed ModuleX. I also tried Module without info group like ModuleZ, same bad result).
Then Added a button to DefaultViewY and a correspondig event-handler to load ModuleA(again, same code as used for ModuleX). Everything compiles fine so far and i can load ModuleX but not the new ModuleA:(
I then used debugger to look whats happening and some strange behaviour appeared to me. The problem takes place in
public virtual IEnumerable<ModuleInfo> CompleteListWithDependencies(IEnumerable<ModuleInfo> modules) of
At the end of this function there are these 2 code lines
IEnumerable<ModuleInfo> sortedList = this.Sort(completeList);
completeList contains one entry for ModuleA, looks good too me so far. But after
this.sort(...) sortedList is empty(null to be correct).
So i changed code to return completeList; and ModuleA appeared:) But after that, ModuleX (which has no code changes done by me at all) from the sample does not work anymore.
Again i used debugger, and navigated through the code, and i saw that modulemanager thinks ModuleX has 2 dependencies (ModuleY and ModuleW). But i can't see these dependencies from ModuleCatalog.xaml and for some reason needs a sortedList (mabe anyone can
tell me whats the reason for sorting). So changing code back to what it was, helps for ModuleX, but then ModuleA does not work. So where i'm wrong?
Thanks for your help, Joachim