Hi,
As far as I know, there are no previous reports from users about not being able to run the application from the Release folder. As a quick test, I tried this with the Modularity QuickStart, which loads modules using several approaches and it worked correctly, so it doesn't seem to be a bug in Prism.
Based on your description, it seems that your application looks for the module files correctly (that is why it throws an exception when you remove a module dll), so there might a problem during the initialization of the modules. As a starting approach, you could temporally modify the modules to log or show an message when they finish their initialization logic (for example, at the end of the Initialize method) to check that the modules are being initialized. Also, you can subscribe to the LoadModuleCompleted event to check if a module has been correctly loaded or not:
Another point that might be worth checking are the Regions to ensure if the views are being correctly injected or not.
On a different note, you mentioned that you are obtaining the ModuleInfo of each module from a database. Are you using a custom ModuleCatalog / ModuleTypeLoader to load the modules using the database directly or are you using the default implementations and simply passing the ModuleInfos obtained from the database? If you are using a custom implementation your problem might be related to it.
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini
As far as I know, there are no previous reports from users about not being able to run the application from the Release folder. As a quick test, I tried this with the Modularity QuickStart, which loads modules using several approaches and it worked correctly, so it doesn't seem to be a bug in Prism.
Based on your description, it seems that your application looks for the module files correctly (that is why it throws an exception when you remove a module dll), so there might a problem during the initialization of the modules. As a starting approach, you could temporally modify the modules to log or show an message when they finish their initialization logic (for example, at the end of the Initialize method) to check that the modules are being initialized. Also, you can subscribe to the LoadModuleCompleted event to check if a module has been correctly loaded or not:
Another point that might be worth checking are the Regions to ensure if the views are being correctly injected or not.
On a different note, you mentioned that you are obtaining the ModuleInfo of each module from a database. Are you using a custom ModuleCatalog / ModuleTypeLoader to load the modules using the database directly or are you using the default implementations and simply passing the ModuleInfos obtained from the database? If you are using a custom implementation your problem might be related to it.
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini