S
Scott M.
Say I have an .asmx that has been in develoment in my local IIS virtual
directory and I've been accessing it with a development version of a client
(also in local IIS virtual directory). Everything works fine.
Now, I deploy my webservice (.asmx) to a production server (also running
IIS, but obviously in a different virtual directory).
Sure, I could just re-make my client's web reference to point to the new
location for the web service, but there must be some way to deal with this
situation without remaking web references. Is there something I can do in
web.config or in my client code (the service proxy's .URL property?) to
modify the existing web reference to point at the new location?
Thanks.
directory and I've been accessing it with a development version of a client
(also in local IIS virtual directory). Everything works fine.
Now, I deploy my webservice (.asmx) to a production server (also running
IIS, but obviously in a different virtual directory).
Sure, I could just re-make my client's web reference to point to the new
location for the web service, but there must be some way to deal with this
situation without remaking web references. Is there something I can do in
web.config or in my client code (the service proxy's .URL property?) to
modify the existing web reference to point at the new location?
Thanks.