You could try building and deploying you app from the command line -
this way you can just add all of the deployment destinations into the
build script. Theres a good article on it here
http://msdn2.microsoft.com/en-us/library/ms165431(VS.80).aspx
Obviously, I have no idea about your situation but Id be questioning
why the app needs to be published to 10 different locations
Nick
On Dec 15, 9:59 am, "Ronald S. Cook" <r...@westinis.com> wrote:
> We have a Win app that we publish via built-in ClickOnce. However, we have
> 10 different locations to which we deploy the app. Each time we have a new
> build to publish, we have to change the IP in a setting and also in the URL
> to where we want it to publish.
>
> Last night, we caused a problem as published the wrong connection string to
> one of our locations. Its also tedious doing this 10 times.
>
> Is there anyway to more automate this?
>
> What would be ideal is if we could maintain a text or XML document of
> settings and then have some automated script that would automate the
> insertion and publishing n times.
>
> I'm guessing the responses I get will say ClickOnce is great but very
> limited and I'd need to use Windows Installer (msi file), right? I hope not
> as ClickOnce is very easy to use.
>
> Thanks,
> Ron
|
Similar Threads
