Hi Handy Surya,

Thanks a lot for the answer which is spot on and the code snippet .

I guess I do not need to write the piece of code(shown below)  in the shell Downloaded event handler but rather do it when the xap is downloaded.

IdeaBlade.Core.Composition.CompositionHost.Add(ApplicationPackage.Source);

Could you also enlighten me why MEF is not used in ClientUI ?

Regards

Balachander

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 Jimmy,

Thank you very much for the succinct reply.

It has helped clarify all my questions and also explained the behaviour I had with WCF Ria.

Thank a lot.

Regards

Balachander

 

 

Hi Balachander,

Thanks for pointing out about the WCF RIA article.

WCF RIA includes a very limited support for client-side caching, which we don't consider it as a full-featured client-side caching. Its implementation is very simple where the retrieved entities will be cached only in query-level session. This means that if you loaded the first page and have some changes, then go to the next page, the previous changes will be gone because they aren't persisted.

That kind of caching, for me, is not called client-side caching. It's just saving the retrieved entities temporarily for a single session operation which is not useful in advanced scenarios (because it invalidates the use of editing and changes tracking).

Contrary, DevForce implements client-side caching which means the changes you made on previous entities will not lose when you perform another server operation. This enables the batch update feature to be implemented, because it allows you to make changes on first page, jump to next page, do some more changes, and finally click the save button to submit all changes that you've made across the pages.

WCF RIA is good and maybe sufficient for basic and simple scenarios such as per-row editing. Our data controls fully support WCF RIA as well, so the choice between WCF RIA and DevForce lies in your scenarios and business requirements. If you're implementing mission-critical apps, I would suggest DevForce because you get first-class products and support. I recalled my poor experience submitting feedback and bug fixes to WCF RIA team and never get responded in years -- I think we cannot expect too much on a free software, can we?

Hth,
Jimmy

Hi Martin,

Thanks for the update.

My understanding on WCF RIA is that entities retrieved through a query ARE CACHED on the client side. 

http://blogs.msdn.com/b/digital_ruminations/archive/2011/01/05/ria-services-output-caching.aspx

http://www.softinsight.com/downloads/DevConnections/Noyes_SLC_LDA302_DeepDiveIntoRIAServices.pdf

So why this restriction ?

How is the use of QueryDescriptor comparable to the DCV introduced in RIA Sp1 ?

Balachander

 

Hello Balachander,

Bacth Update is not available while using WCF RIA because WCF RIA doesn't support what we called Client-side caching. Therefore, it will retrieve all data from the server-side and overide all changes in the UXGrid.

Client-side caching is needed when we perform Batch Update. Since it is not supported in WCF RIA SP1, then we couldn't use the behavior of Batch Update process. However, DevForce does support client-side caching and that is why we can implement Batch Update when using DevForce.

Hope this helps. Thank you.

 

Regards,
-Martin-

 

 

Hi Jimmy,

Discovered the problem......  the folder name BusinessApplication.Web in the zipped template file has now changed to BA.Web

• The zipped template file has to be changed as follows
• Unzip the Business App Template file to a folder say My Intersoft Business App
• Examine the contents of the above mentioned folder
• You will find a folder BusinessApplication.Web
• Change the name of the folder BusinessApplication.Web to BA.Web
• Zip the My Intersoft Business App
• Replace the original zip file with this generated file

Regards

Balachander