How to open a WCF RIA Services application to other type of clients: the OData endpoint (2/5)

re: How to open a WCF RIA Services application to other type of clients: the OData endpoint (2/5)

Anthony White — Mon, 21 Mar 2011 13:31:40 GMT

Hi David,

very useful info you have put together here. Do you have anything to add on validation? particularly sharing rules between entity framework/ria services and mixed clientss e.g. Silverlight and ASP.Net. How would you do this?

Thanks Again

re: How to open a WCF RIA Services application to other type of clients: the OData endpoint (2/5)

David Rousset — Mon, 10 Jan 2011 10:51:21 GMT

Hi Stijn,

No, you should rather use the SOAP endpoint of your RIA Services layer for your WP7 client. I've shown you a sample here : blogs.msdn.com/.../how-to-open-a-wcf-ria-services-application-to-other-type-of-clients-the-soap-endpoint-3-5.aspx on how to expose the RIA Services layer via SOAP for a WP7 client. You will then have a full CRUD support + entities model created on the client thanks to this SOAP endpoint.

Regards,

David Rousset

re: How to open a WCF RIA Services application to other type of clients: the OData endpoint (2/5)

Stijn Liesenborghs — Mon, 10 Jan 2011 07:52:06 GMT

Hi David,

Nice Series,

Currently I am struggling with a project where I want to reuse the Ria Services of a silverlight app in a WP7 app.

Since Consuming an OData service is the only built in support for WP7 at this moment, I exposed my Ria Service as an OData endpoint. All works fine except. When consuming a plain old WCF Data Service the entity references are created into the model I generated with the DataSvcUtil. But this is not the case when I consume a WCF Ria Service that was exposed as a OData Endpoint.

Any Ideas? Or suggestions on Reusing existing WCF Ria Services on a WP7 app without losing entity references.

Thx in advance.