I have an install program. It installs the exe written in C#, with an app.config which points to a web service.

I have no idea where the web service will be once deployed. How do I manage this?

djc

Good question. You need to have some controlled endpoint otherwise you would have to communicate something to everyone who has installed this application. Could you put some kind of lookup into the application? Perhaps put an XML file on a web server somewhere, and your app looks at that for the address of the web service? One way or another you need to put something somewhere that you can establish and control the information.

Playing a technical devil's advocate: How can you deploy a client app that uses a web service that is not yet deployed?

-Peter
peterlanoie.blog

Devil's advocate?

We put all data access into web services. They tend to be application specific. So we deploy the web service on the company network server. Then we deploy the app on the client workstations.

It's hard for me to believe that this problem doesn't come up all the time. But I haven't found an answer for it. Your tentative solution kind of begs the questions. If the app can find an XML file on a web server, it can find the web service.

But thanks.

So then how do you not know what the web service address is if it's deployed?

-Peter
peterlanoie.blog