Mar 21, 2013 at 8:23 PM
Edited Mar 21, 2013 at 8:30 PM
Based on your findings, I believe we could say that your application is correctly loading and initializing the modules and this problem might not be related with them.
The next "suspect" we could analyze is the UI Composition
logic of the application: if the modules are being loading correctly but the views are not being shown, there might be a problem when injecting the views in the regions. Now
that you mention that you are using Navigation
, I believe that it's important to note that
Prism's Navigation API
automatically swallows any exceptions that might arise during the navigation process. As a result, if an exception is thrown in a
the view is not injected in the region, but the application doesn't crash. In order to find if an exception is being thrown during a
, you can either subscribe to the NavigationFailed
event of the
or pass a callback to the RequestNavigate
method. You can find more information about this in the following chapter of the
As to why this is happening when building in Release
and not in
, my guest is that it might be related to a timing issue. Based on my understanding, when building in
, the compiler optimizes the code in order to improve the performance and therefore, it might be possible that a hidden timing issue in the application could appear as result of the performance improvement. An example of a timing
issue, if the ContentRegion
is not created before the Navigation Request
is invoked, it will fail.
If this does not help in finding the cause of the problem, it could be useful if you could provide us with a repro-sample application that we could analyze in deep so that we can help you further with this.
Finally, as a quick test, try to build your application in a different computer just to check if this is not something generated by your
I hope this helps,