Hello Agustin,
Thanks for your assistance. I have already subscribed to the ContentFrame_NavigationFailed method in the Shell. The failure does behave like an exception has occurred, but I have not been able to trap the event in my try/catch blocks.
I do have two levels of Prism modules being loaded in this case. After the main prism module for the page is loaded, 1 of N sub-modules is conditionally loaded based upon user choices that occur prior to loading the main prism module.
Is setting the NavigationCacheMode to Disabled not supported with Prism? In other words, is the Module Manager incapable of dealing with my stated two-tier module Page scenario by design?
If the above configuration is not supported in Prism, then the second issue, no visible exception thrown, is probably a mute point. Although, I would like to figure out what is masking the apparent exception which produces the white screen of death.
Thanks, Warren
