In this article Tim Heuer concentrates his attention on RIA Services deployment.
So you’ve been playing around with Silverlight and WCF RIA Services (the artist formerly known as .NET RIA Services) and you are ready to deploy. You’ve been living in your happy Visual Studio environment, perhaps even relying on the built-in web server (a.k.a. Cassini) to serve up your pages/XAP to test. All has been well, you’ve done your testing and you are ready to publish to your server. You compile one last time and then right-click in Visual Studio on the web project and click Publish. You push to your IIS endpoint or via FTP and the files deploy. Sweet! Now you go visit your site. And it doesn’t work.
Michael Washington posted a tutorial on using WCF RIA Services with DotNetNuke. This tutorial demonstrates creating a simple module that allows each registered user of a DotNetNuke website to create and edit their own Task list.
This tutorial will also cover two important issues that are of interest to DotNetNuke module developers; implementing WCF RIA Services in a non WAP website, and securing and segmenting data for website users.