views:

1640

answers:

2

I have a silverlight control which has a reference to a silverlight enabled wcf service.

When I add a reference to the service in my silverlight control, it adds the following to my clientconfig file:

<configuration>
    <system.serviceModel>
        <bindings>
            <basicHttpBinding>
                <binding name="BasicHttpBinding_DataAccess" maxBufferSize="2147483647"
                    maxReceivedMessageSize="2147483647">
                    <security mode="None" />
                </binding>
            </basicHttpBinding>
        </bindings>
        <client>
            <endpoint address="http://localhost:3097/MyApp/DataAccess.svc"
                binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_DataAccess"
                contract="svcMyService.DataAccess" name="BasicHttpBinding_DataAccess" />
        </client>
    </system.serviceModel>
</configuration>

How do I specify a relative url in the endpoint address instead of the absolute url? I want it to work no matter where I deploy the web app to without having to edit the clientconfig file, because the silverlight component and the web app will always be deployed together. I thought I'd be able to specify just "DataAccess.svc" but it doesn't seem to like that.

+2  A: 

You can't use relative URIs in client endpoint configuration. What you can do is just add another constructor to your proxy class that will take some sort of URL parameter that you can perhaps get from another config value or use one of the Dns class methods.

Strelok
If I were to take this approach, Where would I put my relative url parameter? I'm looking at the ServiceReferences.ClientConfig and I don't see a spot to put it - it doesn't seem to have the same elements ans a web.config file.
Jeremy
+9  A: 

My solution:

Instead of using the devault constructor (which uses the ServiceReferences.ClientConfig file) to instantiate my proxy class, I use the following:

svcMyService.DataAccessClient svcProxy_m;

System.ServiceModel.BasicHttpBinding binding = new System.ServiceModel.BasicHttpBinding();

/*
Create an end point, build a an absolute uri reference by specifing the host address and a relative referece to the service page.
Application.Current.Host.Source will be something like Http://server/app/ClientBin/SilverlightApp.xap"&lt;br/&gt;&lt;br/&gt;
Specifying Uri(Application.Current.Host.Source, "../DataAccess.svc")); will return "Http://server/app/DataAccess.svc"
*/

System.ServiceModel.EndpointAddress address = new System.ServiceModel.EndpointAddress(new Uri(Application.Current.Host.Source, "../DataAccess.svc"));

svcProxy_m = new svcMyService.DataAccessClient(binding, address);
Jeremy
+1 just solved my Silverlight deployment problem.
geofftnz
I would think that the behavior described here would have been default silverlight behavior. I'm puzzled that we would need to do this for every project. :(
Jeremy