Jul 3, 2010 at 1:25 PM
Edited Jul 3, 2010 at 1:38 PM
I have problems with Navigation Framework in the scope of a single external xap loaded via Deployment catalog. All your MIX10 demos work fine but you deal with Pages loaded from external xap, no samples on using both the Frame and Page. It seems that there
are some problems related to type resolution or something like that. We have chart modules with drill-down navigation support that rely on SL4 Navigation and there's no way easily replacing existing functionality with some sort of workarounds :(
You can easily reproduce this issue with your "MefNavifation" sample from MIX10 demo. Open "Orders" project and add a new page called "Order1". Now go to the "Orders.xaml" and put the following like somewhere inside
Try launching solution and navigating to the "Orders" page. You will get an exception saying there are some problems finding the underlying type for "Order1.xaml". Sometimes I get problems even with addressing images within the page living
inside separate package. I've tried all the alternatives like specifying frame source from code but nothing helps for the moment. The temporary solution for my project was adding a direct reference to the library instead of loading it via DeploymentCatalog
and that helped resolving navigation issue (however this is not the desired design for the project).
Any ideas why it is happening with URIs and Navigation?
Thanks in advance,
P.S. This thread also addresses this problem I think: