Need a simple CRM and Project Management system?
Check out JobNimbus - CRM for Contractors and Service Professionals.

Tutorial for Configuring Silverlight 4, Entity Framework and WCF RIA Services in Separate Component Assemblies (DLL’s)

Why does Microsoft assume that we want to combine our business, data access, service, and web layers together in a single web project? Without sounding too much like a rant here, take a look at almost ALL of Brad Abrams (former Microsoft Architect for WCF RIA Services and Entity Framework) posted examples of how to use the Entity Framework with RIA Services. They all have the Entities, RIA Services, and pretty much all of the other data logic included in the Web Application project.

Obviously, this does not promote re-use of the single most shared component in most enterprise companies systems, the Data Access Layer (DAL). Not many are going to need to reuse the domain services generated for a project because they are going to have a lot of hard-coded logic that is specific to an application (maybe that is debatable because you could design this for a lot of reuse) but many applications access the same database and having to rebuild the same model, maintain it in multiple projects, and any customizations and validation you add very problematic. Since the inclusion of the great visual designer tools in the first version of ASP.NET, Microsoft has been on this path of tightly coupled, small project coding that makes reusing something as a component/assembly/DLL in another project difficult if not impossible.

Silverlight Issues with Coupled Components

Unfortunately, this trend is continuing with the amazing Silverlight/RIA Services/Entity Framework stack which is really awesome. I can’t say enough great things about it but I really have to take issue with the assumption about tight coupling. Yes, if your project is small and you have a small database and you are only one of a few developers and work on a single product (BTW: This is probably the majority of software projects so that is why they have focused on this), then this solution works great. If you have multiple products that access the same database, have to create API/Web service access to your systems, have to share code with 100’s of developers, or need to reuse components and libraries across lots of projects, then you will be left scratching your head on examples. The same thing for how Microsoft is showing examples for Silverlight applications.

So here we have put together a tutorial for how to create a project with your DAL, RIA Services, Web project, and Silverlight components all in separate assemblies. These assemblies are reusable and can be shared across applications. This also has the nice benefit of organizing the code and keeping every assembly focused on a single capability.

Project Structure

I want to say a few things about project structure and naming with Visual Studio 2010. Here is a screenshot of the project structure:

Although not specific to implementation, we use a naming convention where we preface project/namespaces for Silverlight assemblies and web applications with “client” and assemblies and web projects that are specific to be run on the server are prefaced with “server”. I know, I know, there are already icons for these types of projects to help differentiate them but the icons are so small and look so similar to it hard to track. Also, it is nice to have a namespace that tells you in the code where a particular object or component maps to.

Description of Project Structure

The projects listed here are as follows:

EntityComponentTest.Client.Data – This is a stub for the data access layer on the Silverlight side. This assembly interacts directly with the server’s Entity Framework DAL layer.

EntityComponentTest.Client.WebApp – This is the Silverlight web application where the XAP is compiled into. This contains App.xaml and MainPage.xaml.

EntityComponentTest.Server.Data – The DAL for the application. This is where the Entity .edmx files are located.

EntityComponentTest.Server.Service – This is where the WCF RIA Services which use the Entity Framework objects to pass data to and from the database to the Silverlight client.

EntityComponentTest.Server.Web – The web project where the pages that host the Silverlight XAP are hosted.

Creating the Projects

Here are the basic steps to get this all working. Once you’ve created your solution to hold these projects, first add the server-side projects.

NOTE: To get this to work right, you need to make sure all the tools for Silverlight including the RIA services toolkit are installed on your development machine. You can get the tools here:

Create a new ASP.NET web project and name it according to your naming standard. This will be where the Silverlight XAP is hosted. (EntityComponentTest.Server.Web)

Create a new Class Library for the DAL layer. This is where your Entity Model (edmx) will be placed. (EntityComponentTest.Server.Data)

Create a new Class Library for the WCF Services. This is where your WCF RIA services will be placed. (EntityComponentTest.Server.Service)

Create a new Silverlight Class Library for the DAL stub on the client side. Make sure this is a Silverlight assembly. (EntityComponentTest.Client.Data)

Create a new Silverlight Application. This is the main app that will be packaged in your XAP for the logic of your Silverlight application. NOTE: When you do this, the system will probably ask you if you want to associate this project with your web application. Say yes, and let it create a page for you and hook it all up. (If you forget to say yes here, it is easy in the web project properties to set the Silverlight application later).

Setting References

Set a reference from the EntityComponentTest.Server.Web project to the EntityComponentTest.Server.Service project.

Set a reference from the EntityComponentTest.Server.Service project to the EntityComponentTest.Server.Data project.

Set a reference from the EntityComponentTest.Client.WebApp project to the EntityComponentTest.Client.Data project.

Configure Settings to get WCF RIA Services to talk to Silverlight

A few settings need to be configured in order to get the WCF RIA Services to show up in the Silverlight application. Right click the EntityComponentTest.Client.Data project and choose “Properties” from the context menu. Set the properties on the Silverlight tab for the WCF RIA Services Link to the EntityComponentTest.Server.Web project similar to this screenshot.

Now edit the Web.Config in the EntityComponentTest.Server.Web project so that the services will be able to be served by the web project (basically handles custom pathing for service URL’s and importing the System.Data.Entity assembly. Add this element to the Assemblies section:

<add assembly="System.Data.Entity, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

Add this element to the httpModules section:

<add name="DomainServiceModule" type="System.ServiceModel.DomainServices.Hosting.DomainServiceHttpModule, System.ServiceModel.DomainServices.Hosting, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

Add this element to the System.ServiceModel section:

<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />

Your web.config will look similar to this:

Setting up the Entity Model

Now in the EntityComponentTest.Server.Data project add an ADO.NET Entity Data Model (edmx) file to store your data model.

I have created a simple database table to illustrate the process called “Customer”. Here is a view of what the table schema looks like in SQL Server.

Now connect your entity model to your database and add this customer table to your edmx model. Your model should look like this when you are done.

Setting up the WCF RIA Service

Now we can create a WCF RIA Service to access this table to do selects, inserts, updates, and deletes from the Silverlight client. But MS has made this harder than it should be to get it to work in your loosely coupled project. You have to do a little trickery to get this to work.

NOTE: The reason for this is that the “service.metatadata.cs” files that are auto-generated when the service is added for its Entity model(s) MUST be in the same assembly as the Entity Model (edmx) itself. This is a hard and fast rule. But we don’t want our services (web access layer) in the same assembly as our data model (what if we want to use our DAL layer somewhere else and don’t want to expose it through RIA services?).

To get around this, we first add a Domain Service Class to our EntityComponentTest.Server.Data project first.

This will create the metadata.cs file(s) in the correct place and set your services up right. Then move the newly created “service class” (DevToolShedService.cs in this example) to the EntityComponentTest.Server.Service. Then to get this to fully work in your service assembly, you need to change the namespace for both the DevToolShedService.cs and DevToolShedService.metadata.cs classes to point to the EntityComponentTest.Server.Service. So your Service class should look like this at the top when you are done.

Testing the Application and WCF RIA Services

To test the application, go the MainPage.xaml in the EntityComponentTest.Client.WebApp and add a DataGrid so we can show the list of Customers from our Customer table. You XAML should look something like this:

<UserControl x:Class="EntityComponentTest.Client.WebApp.MainPage"
    d:DesignHeight="300" d:DesignWidth="400">
    <Grid x:Name="LayoutRoot" Background="White">
        <sdk:DataGrid Name="dgTest" AutoGenerateColumns="True" Height="500" Width="500" HorizontalAlignment="Left" VerticalAlignment="Top" />

Now in the MainPage.xaml.cs code behind, we can bind our Customer data to the grid with code similar to this:

namespace EntityComponentTest.Client.WebApp
    public partial class MainPage : UserControl
        public MainPage()

            this.Loaded += new RoutedEventHandler(MainPage_Loaded);

        void MainPage_Loaded(object sender, RoutedEventArgs e)
            // create a context to the WCF RIA service and call the RIA service method
            // to get the list of all customers.
            var context = new Server.Service.DevToolShedContext();
            dgTest.ItemsSource = context.Customers;


Now run your project and you should see a list of customer data from your Customer table working and everything is decoupled (as much as we can in Silverlight) and this makes it easy to re-use your data access layer in other projects without having to bring all your exposed RIA services with it.

You can download the solution and project files for this project here:

Whenever you think associated

Whenever you think associated with nature what do you consider of? Perhaps a sunset, possible the mountain or perhaps a puppy. The most amazing aspect associated with nature may be the fact this exist and we have to protect it's existence in the event that we intend on passing the wonder to the next era.

This informative article will be centering on the attractiveness and style which is included having an Asian room. Particularly, we will give attention to three important areas: top quality design, a confident ambiance, plus the appearance regarding bamboo.

Total natual skin care requires greater than an application of your cream or perhaps lotion. I would really like for one to consider added factors which can be just since important since topical treatment options.

Upgrading to Silverlight 5

I have been using your excellent configuration for some time. But, after a gap in using Silverlight, and returning to it with Silverlight 5, I am getting an error when attempting to access the database; even in the development environment. The error I get is:

"Load operation failed for query 'UspLoginDetailsGet'. The remote server returned an error: NotFound."

UspLoginDetailsGet is the stored procedure I want to call.

Have you experienced any changes to RIA processing when moving from Silverlight 4 to 5.

Thank you in advance.


project all working Now1

Hi, after the second attempt, I manage to get the above project working! Yippee! The next question is, how do I connect the model to a viewmodel using MVVM?. I will be using Prims 4 Framework with MEF.

Excellent Article

Well done, a thoughtful, clear, well written piece.

It answers 90% of my needs but misses on one point.
How can a separate ASP.Net project access the WCFria services like SilverLight does?

I have tried to use the …Test.Client.Data dll and point the URL at ..Test.Server.Web.
You end up in dll hell, with the where is issue.

I have tried sharing the generated file from …Test.Client.Data and ended up in the same place.

If you can crack this, you have created the universal data back end to Silverlight, ASP.Net, Odata, JSON, etc
How cool is that !


Thank you very much...

This is what I have looking for. I did not understand how can I implement repository patter on the server side so that i can use it on client side.

Thanks Bro!!!

Different method to get data widthout DataGrid????

It's very insteressing!
I have a question:

You used this code:

var context = new Server.Service.DevToolShedContext();
dgTest.ItemsSource = context.Customers;

But I can't use this code, it don't returns any items:

var context = new Server.Service.DevToolShedContext();
var _customers = context.Customers;

Customer _singleCustomer = (from rec in _customers
where rec.FirstName == "Unique Bob"
select rec).Single();

Why? How Can I do?

json endpoint

Great sample.
However I tried to elaborate the sample: Customer.Contacts.
Problem: Contacts is always empty on client side.
I tried exposing json endpoint(JsonEndpointFactory) for testing to see if data is not sent by server, or is not de-serialized by client.
getting the error 'Could not load file or assembly 'Microsoft.ServiceModel.DomainServices.Hosting'.
Any ideas anybody.
I have tried copying that dll in any path that I thought would fix, but didn't.

Add Middle tier physical layer

How would you go about setting up this project in 4-tier physical layers, i.e Client -> Web Server -> Middle Tier Server -> Database. Basically I'm trying to add physical layer between Web Server which hosts Silverlight and Database. My current server setting is like this Client -> Web Server -> Database.

what´s the reason of the stub of data in the client?

Nice post.
just that, As an other person that left a comment, i don´t understand the function of the
Can you clear as that.

thanks for the apport

WebPage is unavailable!


firstable, thank you for this awesome post, it really helped me to understand RIA Services.

I downloaded the very project you posted and checked for the changes everybody is speaking of. Everything works fine (build) but when the page is supposed to load i get the following error:

This webpage is not available
The webpage at http://localhost:53599/Default.aspx might be temporarily down or it may have moved permanently to a new web address.
Here are some suggestions:
Reload this web page later.
Error 105 (net::ERR_NAME_NOT_RESOLVED): The server could not be found.

Would u have any idea of what i could start looking for to solve the problem.

I tried on many different RIA Services examples but i always eventually end here!

Thanks for your help!


What to put in EntityComponentTest.Client.Data ?

These days I read this article, and I think it is very valuable one.

As I understand your tutorial, EntityComponentTest.Client.WebApp project will contain App.xaml and MainPage.xaml, and other necessary .xaml views.

But I can't clearly recognise what is purpose of EntityComponentTest.Client.Data project. What will be its content? Please, can you explain that with more details. Will it contain ViewModel part code or code behind part of .xaml files, or ... ?

Thanks in advance.


In yuor example RIA Service generate Generated_Code folder to Cl

Thanks for this example.
Only from it I have understood that it is not necessary to refer directly from Client.WebApp on Server.Data.

As you managed to customise in your example RIA Service to generate a code in Client.Data instead of in Client.WebApp?

By default in my project a code generated in Client.WebApp.

How to customise code generation in RIAService in other assembly?

Thanks for the answer

Service Project Divided

I agree with your point of view regarding the need for dividing a silverlight "business" application into several layers. I think the business application template from Microsoft is a pretty bad idea since in my opinion completely violates low-coupling, high-cohesion principles. So thank you for this posting.

However, there is one thing I don't understand from your approach. To me the problem with adding the Domain Service into a different assembly does not solve the underlying issue. Basically what you have done divide the implementation of the Domain Service across two assemblies. Both assemblies need to reference now framework assemblies which are required to encapsulate a domain service in the library, like: System.ServiceModel.* or System.Data.Entity. The domain service class cannot exist without its metadata counterpart which actually defines the entities in the edmx and carefull consideration is to be taken when updating either of them (for example setting validation in the metadata) on whether it will affect the other. So tight coupling still exist here. The ideal way would be for the Data assembly to contain only Data Access logic and responsability, and the Service Assembly to maintain only Domain Service logic, with a reference to DAL.

I'm not trying to criticize what you have done here, it's actually great that somebody finally addressed this issue with a solution. But this constraint that the metadata cannot be in a separate assembly from the edmx is really stupid and messes things up. I am asking if anybody has found a higly 'decoupled' solution for this.

Best I could do with current tool set

You are exactly right. Unfortunately, this was the best I could do with the current tool set. The RIA Service implementation is tightly-coupled by design so there is virtually no way (without huge pain and suffering and hand-coding) to make it more stand-alone.

I will say that at the very least, separating the DAL from the Services at least allows me to reuse my DAL layer in other projects (which was my main goal here as data access is critical and I didn't want to have to rewrite that many times over). The services are more specific to a given solution so they are not as re-usable anyway in this certain case (although that could be different for your environment).

How To Deploy The Sample In IIS 7

When I try I get 500 error , any solution please ?

Running in IIS7

Have you tried running this under II7, rather than VS Development Server?

When I do this, I get the 'Not Found' error:

'Load operation failed for query 'GetCustomers'. The remote server returned an error: Not Found.'

What am I doing wrong?


Client side config

Thank you for your excellent tutorial.

Forgive my ignorance, but under WPF, using WCF, I am used to having config files for the service project, the data project on the server side and the client side application project.

Why is it that the client side project for silverlight doesn't need a config file with WCF settings?



Thanks for the nice article

I am having an issue when i run the application attached i am getting a message from the browser "The Application was created for an expired beta release of Silverlight. Please contact the owner of the application and have them upgrade their application using an official release of silverlight" How can i get rid of this??

Any help is appreciated

Thanks !!!! :)

Hi, thanks for this tutorial,it is great to finally find some info on this subject. I had had a couple of bumps along the way but it all worked really easily in the end. The issues I found were:

1. Had to copy the Entity model connection string from Server.Data to the web.config in Server.Web.

2.In my service class the Customer in IQueryable was picking up from Server.Service.Customer and NOT Server.Data.Customer, this caused a lot of errors as the service object does not have they required entity properties such as entity state etc. Once I tidied up the reference to use Data.Customer all worked like a charm.

3. Unlike some of the other posters here I only had to make the namespace changes that you specified.


Inserting etc


Thanks for the awesome article. Do you have any examples or links on how to use the insert of delete functions. I keep running in to a 404 error relating to the System.ServiceModel.DomainServices.

Thanks again.

Awesome example

Exactly what I needed to decouple the DAL from the business logic. I did have to go in and modify the Designer.cs module from the .edmx and I think you forgot to mention that in your example. Also, in the Designer.cs class, if there are any relations set up (FK's, etc.), specifically, the code after:

[assembly: EdmSchemaAttribute()]
#region EDM Relationship Metadata
-- relationship metadata in here

that code has to be modified also. Took me a few minutes to figure this out, but I got it and it is working now.

I wish there could be a template in VS2010 to automagically create this and create it as a SL Business or SL Navigation application as I have to add a boatload of References in. May check into this for something to do in my spare time!

Anyway, great example

Handling EDM Relationship Metadata

I am trying to make your design work. It has great promise; however, if EdmRelationshipAttributes are created by the model, how do I reference the various types (EntityComponentTest.Server.Data) within the model from the altered designer.cs (namespace of EntityComponentTest.Server.Service)?


If I manually change the

If I manually change the references to the entities within the block from EntityComponentTest.Server.Data.EntityName to EntityComponentTest.Server.Server.EntityName, then the code builds fine. I'll have to remember to change these if the model is regenerated (well, the compiler will remind me, I'm sure).

I still do not have data populating my grid, though. Hopefully, I'll see what piece of the puzzle I have missing and get this working. I like the structure. Thanks for posting it!

To get the data working,

To get the data working, simply copy the connectionStrings from the app.config of the Server.Data project to the web.config of the Server.Web project. All is good.

More in deep explanation

Thanks for this document. There is not enought about this subject. Great tutorial.

Just some question at respect:

Do i understood?, BLL is still coupled with DAL cuz them are in the same namespace (service), but the benefice of implement that in separate dll´s is that them are independient?

In this aspect DAL yet knows about BLL ?

Thanks in advance, great

Can't get the tutorial code to work as demonstrated.

I've run through your demo 3 times now, and ran into the following problems:

1) The namespace needs to be changed to (Project).Server.Service for the xxxxModel.Designer.cs as well as the metadata, and DomainService files. This is a problem if you make changes to the Domain and it automatically overwrites the file for you constantly.

2) Replicating your example, the Context doesn't get passed correctly through to the .Client.WebApp silverlight app. I keep getting the error Cannot implicitly convert ObjectSet to IEnumerable.

3) The Service application needs references to the System.ServiceModel.DomainServices.EntityFramework (everything added when adding a Domain Service)

4) After all this Silverlight still can't find the correct Context using projection.

So maybe I'm making a big dumb mistake, but this seems to make the separation even more difficult, if you have to rewrite the namespace of the EntityFramework cs file right?

Looks really promising, but leaving those aspects out make it hard to be usable - although your code example works - which contains all the changes above + something I can't find.

Any advice is appreciated. Tks

Sorry to hear your trouble

Man, that is a big bummer. Here is what I can tell you. I did this step by step on my machine and took screenshots of everything as was able to complete it successfully. Many others have emailed me and said they successfully followed these instructions and were able to get it working from the tutorial.

In addition, you can download the exact project I created with all of the code so you could go through in detail and see if any properties or settings or DLL versions are different to help you troubleshoot.

It could be you are running a different version of Entity Framework or RIA than I had installed as well.

For issue one with the namespaces, yes, if you change the domain, you will have to recopy the files. I wish MS would fix this!

Issue 2, I am not sure why you are getting the IEnumerable error. Not enough info there for me to tell.

Issue 3, the service does need a reference but when I did this, it was automatically added by VS 2010.

Issue 4, if Silverlight can't find the context, then it can be one of many reasons but a likely issue could be that you are not targetting the correct RIA assembly in the properties of your Silverlight app.

RIA Service not correctly mapped

There is a huge error in this Tutorial, you are telling people to Reference the WCF RIA Services Link to the Server.Web project, but this is the ASP.NET project, so it will not serve you the context object.

Instead you should point the WCF RIA Service point to the actual service located on Server.Service. Otherwise the Data Lib will not pass the context object trough to the requestor, in this case Server.WebApp.

I think I figured it out.

You're not supposed to do it this way. Try with a Ria Services project first --


tks for the reply

Enumerable: Yeah that's still the issue, and I'm pretty sure its RIA related. I can see it working in your demo project - and yet every time I recreate it, I get the same error. Any idea on paths to troubleshoot? (I did install RIA just last week so I don't know if that's part of the issue)

Scouring all the differences between your working code and the project I developed was how I found that the domain objects were set to Server.Service. Now I also know its generated with a t4 somewhere - if it just gave us access to that t4 then we could adjust it!

About the References:
Well - the service gets its references when you add it to the .Server.Data project, but then when you move it - it doesn't have them anymore. I ended up just creating a blank service and deleting it - which recreated those references. It was just missing from your example is all, only reason I mentioned it.

Again any help on troubleshooting why RIA isn't projecting correctly would be appreciated. Thank you!


In the service if you check the type of inheritance, you will see it is in namespace Server.Data, this is because the Model.Designer file is also in that namespace (Server.Data)... And that makes sence, because you created it there!

If you go and check the example provided, you will see that the Model.Designer file is set to namespace EntityComponentTest.Server.Service ... the thing you need to do to get the solution working is, besides only changing the namespace of the service and metadata file, also change the namespace of the EDMX designer file...

Then the iqueryable will work.

Kind regards

What's the point

I'm missing the point here.
The eventual purpose of your solution is to have a DAL which can be potentialy reused for other purposes. Nonetheless, the 'tricks' with the namespaces cause that your DAL is already semantically linked to the service layer (since the DAL assembly contains the namespace EntityComponentTest.Server.Service).
Correct me if I'm wrong but I don't see any added value. Did you try also custom validations in this configuration?

Kind regards

De-coupling the DAL

It is true that the service layer does have a tight dependency on the DAL layer and yes, you are right, the DAL cannot be removed in this scenario


the DAL does not have a dependency on the service layer so it is free to be copied or referenced by other projects and reused. This is the big benefit, reuse of the DAL layer.

So far in my experience, there haven't been many (if any) occasions where I've wanted to reuse the RIA services only because they are usually coded totally specific for a particular project whereas the database and the DAL are not coupled here and can be resued elsewhere.


I'm not sure if this post is still being monitored, but I've stumbled across it due to the fact that I'm in the process of trying to implement a logically separated solution, and as I get further into it, I'm not clear on why it makes any sense to do this. My main questions are with validation.

The project which contains the .edmx, is that all it is supposed to contain, i.e., structures which only define the data model itself, no validation or any other type of logic, correct? If so, where does the validation logic go? I'm assuming that since the project which contains the model *only* defines the physical model, any and all logic, whether it be CRUD operations and/or validation logic, should reside in the services layer, correct?

However, this seems to go against de-coupling the physical model and service layers, at least the way Microsoft has architected, since the validation metadata pointing to validation methods must be placed on the model metadata, which resides in the model project. In order to have no logic in this layer, the metadata must point to classes which perform the validation in the service layer. To truly abstract the physical model from the service layer, validation should not be a part of the model layer, since if App-A and App-B are both using the same model, they may have different validation requirements. Therefore, in order to implement validation in this way, the DAL *would* in fact need to reference the service layer, and a further complication is that any validation metadata added to the physical layer would have to be specific to a particular service layer...this sort of defeats the whole purpose of physical model abstraction.

Perhaps I'm missing something, but it seems to me that validation extremely complicates this scenario, but I would love to hear the opinions of others.

DevToolShedModel.Designer.cs - Namespace ?


Thank you for these valuable informations.

I've a simple question(maybe i'm wrong ?)

When you create the EDMX in the EntityComponentTest.Server.Data project, the namespace of DevToolShedModel.Designer.cs is set to 'EntityComponentTest.Server.Data'.
Thus, trying to move the metadata file to 'EntityComponentTest.Server.Service' Namespace, will failed.

Looking at your sample, I've seen that the DevToolShedModel.Designer.cs is in 'EntityComponentTest.Server.Service' Namespace.
Have you moved the namespace ? Is this point missing in the tutorial ?

Thanks again for the job.

Compile error with SL4 business app template

Thank you very much for this information, it's really needed! Anyway, I have tried a variation with a VS2010 Silverlight Business application together with its website (e.g. MyApp and MyApp.Web). Everything works fine until in the project I add the WCF RIA services link to MyApp.Web: at this point, I get 5 errors like 'The type or namespace name 'Resources' does not exist in the namespace MyApp.Web' (are you missing an assembly reference?). If I remove the link the application builds fine again. Could you give a hint for using your tutorial with such applications?

Compile error with SL4 business app template

Right, you just need to "include" the Resource files in your SL Class Library (Client.Data).

1.) Create a folder structure in the Client.Data project for the server-side resources. In my case I made it: {ProjectRoot}\Server\Resources.
2.) Now, right click the new "Resources" folder you just created and choose "Add --> Existing Item...".
3.) Browse to your Web solution that is hosting the SL app (Server.Web) and browse down through until your find the Resources folder within it (usually it's just at the root).
4.) Now, select the resource files you need, however, don't forget that instead of clicking the "Add" button, click the drop-down arrow on the "Add" button and choose "Add as Link". In my case, I just needed to add "ErrorResources.Designer.cs" and "RegistrationDataResources.Designer.cs".

That should be it, now your projects will compile.

Possible solution

Without seeing exactly what you code and project set is like, my hunch is that in the case of a business application, you may need to set your WCF RIA Services link to your MyApp.Data server-side DAL layer assembly instead of your web. Also, another idea is to make sure your MyApp.Web has a reference to your MyApp.Services assembly where your RIA services are.

Can you expand this just a little?

I am very new to silverlight and using web services.
Now that I have followed your article and published the web service piece to the server (and moved that pesky app.config connection string to web.config and changed the namespace in that model.designer.cs) everything works swell!!

However, how do I write a brand new Silverlight application that reuses that service? I've seen examples of exposing the RIA Service as WCF/WSDL or OData services, but nothing that allows me to reuse a RIA Service as a RIA Service.

Please help.

Exposing RIA Services to another Silverlight App

This should be relatively easy. Just add another silverlight app to your solution and then follow the steps above to set its references and configuration the same as your other Silverlight application. Then it should run just the same and be able to use the same RIA services layer assemblies.

But how do you do it in a totally different solution?

I would like to create a different solution and access my existing WCF Ria Services that I've built in previous solutions.

Can I do that?