Hello,

Thanks for your feedback. Actually, the runtime licensing tool already supports build automation through command line arguments.

You need to supply five parameters to the runtime licensing executable through command line:

• /assembly
• /product
• /version
• /runtimeLicenseKey
• /output

Intersoft.ClientUI.Licensing.v4.exe 
     /assembly="D:\Assembly\Asm1.dll" 
     /product=Intersoft.ClientUI /version=5.0.5000 
     /runtimeLicenseKey=1234-56789-1234 
     /output="D:\Projects\App1\licenses.islicx"

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