I have been able to reproduce your issue but could not find a fix/workaround for it. My approach updating the code of the
LoadAssemblyFromStream method of the XapModuleTypeLoader class provided by the CAL (this is not the best approach, but if it had worked you could have created a custom module type loader):
private static void LoadAssemblyFromStream(Stream sourceStream, AssemblyPart assemblyPart)
Stream assemblyStream = Application.GetResourceStream(
new StreamResourceInfo(sourceStream, null),
new Uri(assemblyPart.Source, UriKind.Relative)).Stream;
Deployment.Current.Parts.Add(assemblyPart); //This is the new line.
This behavior however, only takes place when loading modules remotely (I have tried loading modules statically and been able to perform navigation successfully).
Bear in mind that Prism-v2 was not focused on providing navigation support, not even for WPF. If you feel that a future version of Prism (which will target Siliverlight 3.0 & WPF 4.0
as David Hill says in
this post) should have this feature, or another one included, you could create an item
in the IssueTracker, so people can vote for it. The team might take it into account for future
Please let me know if this helps.