I am running into deployment issues for a SL3, WCF application that runs fine on development machine on built in server as well as deployed on development machine IIS (it is on XP and hence IIS 5.1). Note that the service accesses some data files that are mirrored on dev. server but ultimately has to be using deployment server data. However, when I try to deploy on production server, I get a strange WCF service exception on Async operation. I have done the following:
a) changed the service.clientconfi g to point to deployment server URL and not local hose b) In the web.config service endpoint also points to the deployment server URL and point to the data XML files on the deployment server (app settings section)
Strangely, if I hack the XAP file to have its service.clientconfi g point to my dev. server URL, the deployment server works fine since the service (presumably everything is now pointing to dev. server) is able to now find the data on the dev. server.
Also if I go to IIS virtual directory and do browse on service.svc file, that works fine.
I have seen chatter on the net about changing URL on client config is not enough and has to be done in code such as:
Uriuri = new Uri(Application. Current.Host. Source, "../Person.svc" ); PersonRef.PersonCli ent client = new PersonRef.PersonCli ent("CustomBindi ng_Person" , uri.AbsoluteUri) ; I cannot seem to find the missing piece. Can someone help out by at least pointing me to some checklist of things I should look for?
Thanks Sunil