Hi Chris,

Thanks for your feedback.

We're currently working with IdeaBlade team to deliver a more elegant and future-proof solution to this problem.

Best,
Jimmy

Dear Peter,

Theoritically, the licensing should work in any compatible container that is used as the root visual. It might fail if Lightswitch used certain containers that are not native to Silverlight.

Yes, we'd be interested to investigate the licensing issue further and possibly include full support for Lightswitch in the upcoming service pack release. Please attach a simple sample that replicates the problem.

Your contribution is highly appreciated. Thanks!

Best,
Jimmy

Hi Alastair,

Thank you for providing a simple working sample.

Using the development's nightly build, it's confirmed that the OriginalUri is now captured properly. As the results, your application will automatically navigate to the Settings page after the successful login. This has been tested to work properly, and should exhibit identical behaviors and results as in the Silverlight counterpart.

The fixes for the ExtraData will be included in the upcoming hotfix scheduled later this month. If you preferred to receive the nightly build for early testing, please send an email to technical [at] intersoftpt.com and also please specify your subscription ID.

Thanks,
Jimmy

Hi Richard,

Thanks for your feedback.

Yes, we will support load and save layout settings in the next build.

Regards,
Jimmy

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