One thing you might want to take a look at, is setting up a UDDI
server. It can be used to manage your web services in a central
location. Your client applications can easily query your UDDI server to
find the current location of you services. When you move a service, you
just update the setting in the server and all the clients will point to
the new location.
Windows 2003 ships with a UDDI server component . You can check out the
following links for more info.
Another thing you can look at, is just setting the URLBehaviour
property of your web reference to dynamic. With this setting, the URL
of your web service is stored in your web.config. This would allow you
to avoid having to recompile your application. However, you would still
have to redeploy a new web.config. Therefore, I would recommend the
Hope that helps