Hi Jimmy,

Yes, the external xap calling and integration code as implemented in the sample project is something I would like to understand.

Specifically I am able to navigate to a  page defined as the main type in an external xap using the  VirtualPathIdentity.

I am not able to navigate to another page in the external xap using the VirtualPathIdentity/pagename. 

In the sample solution you have a file Applications.packages which holds the list of Apps (projects) which are added to the Shell in the App.xaml.cs of the Intersoft.ClientUI.Samples project.

When the navigation is made to any other project the appropriate project is downloaded  and control is transferred by the ClientUI Navigation to the appropriate page.

 In all the projects (refer file Application.packages) reference is made to the (EntryPointAssembly="Intersoft.ClientUI.Samples.Framework" and MainType="Intersoft.ClientUI.Samples.Framework.MainPage")

The sample app uses the VirtualPathIdentity to navigate to a specific page on the external xap for example /BarMenuControls/UxToolbar even though the MainType is MainPage.

 

Can you explain how this is done ?

Regards

Balachander

 

Hi Balachander,

Unfortunately, the sample framework project is not currently shipped along in the installer. It contains a number of application-specific logic that we don't feel necessary to be included as source. However, we will consider to include the project source in the next release.

Are there any specific code/features that you are looking for?

Best,
Jimmy

Hi Balachander,

Good questions!

The sample framework, which contains the main type that you referred, actually has nothing to do with the navigation. Most of the packages are referring to that specific main type because we've created reusable components to address various needs of the control examples in the sample framework assembly. This enables the code to be reused and maintained easily, and also allows us to create new samples in very short times.

The ClientUI live sample actually uses nested frame. This might be the part that you missed. The "sub" paths such as "/UXToolBar" in "/BarMenuControls/UXToolBar" is actually processed as the child navigation, which is handled by the child UXFrame inside the sample page.

Since nested navigation is fully supported in ClientUI's navigation framework, it automatically matches the URIs to the defined UriMapping in the child UXFrame, and load the page accordingly. You can learn more about child navigation here.

Hope this helps,
Jimmy

Hi Jimmy,

Thank you for the excellent reply. It provided a clue to what I had missed.

The power of the external xap navigation with virtualuri is fantastic....

Thanks for the really wonderful navigation framework design which is also surprisingly simple to implement !!!!

I had missed having a UxFrame in the external xap project which handles the (child) navigation to transfer control to the desired page. (UxFrame inside the sample page in the sample framework project)

I really love  your precise (on the dot)  replies to my questions.

Regards

Balachander

Hi,

Where could I get the source code of  the sample in Intersoft  ? Thank you!

I’d like to suggest you to install the most recent version of WebUI Studio suite, Intersoft WebUI Studio 2011 R2 SP1, in order to get the source code of ClientUI samples locally. Please click here to download the trial version of Intersoft WebUI Studio 2011 R2 SP1.

Please feel free to let us know, if you have other questions.