Silverlight 3 Modular & WCF reference issues

Question

0.00/5 (No votes)

See more:

I'm busy with a Silverlight 3 project for the purpose of learning Silverlight. I'm working from this example:
Building Modular Silverlight Applications[^]

I've got it all to work just fine, but I'm finding it a bit difficult to get my WCF service so it would work properly across all modules and Silverlight and WCF are both pretty new to me. So now I'm somewhat stuck. To have access to my service through all my modules I have to add a reference to the service in each module. This seems redundant to me.

So my Question here is: Is there a way to have a single reference to the service and then have all the modules work from that single reference?? Something like a wrapper class maybe or interface?? I just don't know how to implement something like this with silverlight and WCF.

I hope my question makes sens.
Thanks

Posted 12-Jan-11 0:00am

NeCroFire

Add a Solution

2 solutions

Solution 1

I got it to work they way I wanted... sorta. I created another project in my solution and added the Service reference to it. Then I just reference the new project in all the modules. So I have access to everything in the service in all my modules. But the app would still not run. I now still have to have the "ServiceReferences.ClientConfig" file included in each module .xap so the module can actually call the service.

I'll keep looking for other ways though, but for now this will do.

Posted 12-Jan-11 1:26am

NeCroFire

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Abhinav S · Accepted Answer · 2011-01-16T02:49:00

Solution 2

Make sure all your cross domain / client access policy files are in place.

Posted 16-Jan-11 2:49am

Abhinav S