To revert back to 6.0.9, please uninstall the newer version, then install 6.0.9 using the DevForce installer located in C:\Program Files (x86)\Intersoft Solutions\Intersoft WebUI Studio 2011 R1\Installer.

Hope this helps.

	<Grid x:Name="LayoutRoot">              <Intersoft:UXWindow Header="Hello" IsActive="True" IsClientVisible="True" HorizontalAlignment="Left" VerticalAlignment="Top"/>
	</Grid>

Hello,

Local page navigation in externally loaded application is already supported in nested frame scenario. This means that each external app has its own UXFrame which is responsible to define its own UriMapping. In real-world scenarios, the shell has no knowledge about the applications that will be loaded, and what mappings that it needs to define in order to route the application's pages properly. In short, the mappings are all defined in each external app's UXFrame which serves as the child navigation. This allows the sub-paths, i.e., /App1/SubPath1 to be translated automatically according to the defined mappings.

However, looking at your scenario at a glance, you don't seem to define UXFrame in each external application, is this correct? Presuming this is correct, we would like to learn your scenario further to understand what you're trying to do with the sub-paths in the root navigation frame. We will also need a simple working sample that illustrates this particular scenario to allow our engineers to implement the best solution with solid architecture.

To give you a quick insight, if we have to support the sub-paths navigation in the root frame, the architecture shall allow developers to define the mappings "externally", not in the UXFrame as shown in the vanilla sample above.

I look forward to your response and a working sample to address your specific scenario. Let me know if you have any questions.

Best,
Jimmy