Greetings,

I have been developing a PPC application which calls a web service on
the WLAN. I've just been using the IP address to find the web service
in VS. I ran into an interesting problem when I went to test at a
customer site, because their server does not have the same address. VS
is assuming that when you use a web service, it's universally available
on the Internet. However in this case we're just accessing local data,
and the only reason we're using web services is that the tools we have
available aren't supported on any handheld platforms.

Obviously VS needs to be able to find the web service in order to
construct its interface, so I have to be able to reference our version
on our server, but then change the URL for deployment. Does anyone have
any suggestions on this? I was wondering if we could use a subdomain
like ws_sub.ourcompany.com. The name ourcompany.com would still go to
our Internet web site, but the local DNS could point ws_sub to the
in-house server.

Thanks,
Dave

RE: Local web service address by kmx

kmx
Wed Aug 30 08:00:02 CDT 2006

Hi DaveO,
Your proxy class will have a property called Url
By default it will point to your development service, but you can just set
the property to the "real life" service when required.
Check the online help for WebClientProtocol.Url Property (i believe that's
where you inherit it from).
Karin

"DaveO." wrote:

> Greetings,
>
> I have been developing a PPC application which calls a web service on
> the WLAN. I've just been using the IP address to find the web service
> in VS. I ran into an interesting problem when I went to test at a
> customer site, because their server does not have the same address. VS
> is assuming that when you use a web service, it's universally available
> on the Internet. However in this case we're just accessing local data,
> and the only reason we're using web services is that the tools we have
> available aren't supported on any handheld platforms.
>
> Obviously VS needs to be able to find the web service in order to
> construct its interface, so I have to be able to reference our version
> on our server, but then change the URL for deployment. Does anyone have
> any suggestions on this? I was wondering if we could use a subdomain
> like ws_sub.ourcompany.com. The name ourcompany.com would still go to
> our Internet web site, but the local DNS could point ws_sub to the
> in-house server.
>
> Thanks,
> Dave
>
>