Hi Federico,
thank you for you reply.
I'm using Prism 4.1 in Visual Studio 2010 Ultimate (version 10.0.40219.1 SP1) with .NET 4.0. As a container I use Unity.
I add all the module to the ModuleCatalog in the bootstrapper with InitializationMode = When Available.
Modules info are stored in a databse table and the module dll are put in the same direcotry as the executables (bin\Debug or bin\Release) and load from there.
I tried to remove one of the faulty module dll and the application give me an exception at start up. With all the modules dll in place the application starts up correctly, but then it seems that the view are not displyed in the regions (I use a tabbed region).
What it is really strange is that this happens only running the application from bin\release and only for certain modules, whose difference from the others I'm not able to cacth.
Regards
Massimo Landi
thank you for you reply.
I'm using Prism 4.1 in Visual Studio 2010 Ultimate (version 10.0.40219.1 SP1) with .NET 4.0. As a container I use Unity.
I add all the module to the ModuleCatalog in the bootstrapper with InitializationMode = When Available.
Modules info are stored in a databse table and the module dll are put in the same direcotry as the executables (bin\Debug or bin\Release) and load from there.
I tried to remove one of the faulty module dll and the application give me an exception at start up. With all the modules dll in place the application starts up correctly, but then it seems that the view are not displyed in the regions (I use a tabbed region).
What it is really strange is that this happens only running the application from bin\release and only for certain modules, whose difference from the others I'm not able to cacth.
Regards
Massimo Landi