Hi,
I am not familiar with the module catalog / module loader you are mentioning, but as a possible approach I believe we could start by checking if the cause of this behavior is related to the modules or not. For example, you mentioned that you are using a modified version on this PrioritizedDirectoryModuleCatalog . Does this behavior also happen when using the original PrioritizedDirectoryModuleCatalog ? Also, it could be useful if you could check your modules against Prism's default DirectoryModuleCatalog to see if the modules can be loaded correctly.
Another thing we can check are the differences (if any) between the Domain Module and the other 3 modules in order to find why the custom PrioritizedDirectoryModuleCatalog behaves differently with it than with the rest of the modules.
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini
I am not familiar with the module catalog / module loader you are mentioning, but as a possible approach I believe we could start by checking if the cause of this behavior is related to the modules or not. For example, you mentioned that you are using a modified version on this PrioritizedDirectoryModuleCatalog . Does this behavior also happen when using the original PrioritizedDirectoryModuleCatalog ? Also, it could be useful if you could check your modules against Prism's default DirectoryModuleCatalog to see if the modules can be loaded correctly.
Another thing we can check are the differences (if any) between the Domain Module and the other 3 modules in order to find why the custom PrioritizedDirectoryModuleCatalog behaves differently with it than with the rest of the modules.
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini