Click here to Skip to main content
13,202,706 members (54,785 online)
Rate this:
Please Sign up or sign in to vote.
See more:
We have a very large, very slow, distributed network.

On the network we have a Main central server, as well as a smaller server at each individual site.

Since we have slow lines, and our application is quite large (20MB) we cannot have all our client PC's (300+) installing/updating the application from the Main central server, so I create separate ClickOnce Deployments for each site respectively.

This allows the majority of our users to install/update the application over a fast LAN connection from their local server.

However, the more sites we add the more cumbersome this gets since I have to publish a separate copy of the application for each and every site, each time making sure that I don't mess up the URL's etc. (This happens quite easily)

Is there a way to change the Installation URL & the Update Location URL after publishing the application (preferably programmatically)?

If this is possible, I will create a distribution system that uses a single ClickOnce deployment, modifies it for each server, and copies it to the correct location on each server.

If this is not possible, I will have to continue publishing separate deployments per site and this will most probably force us in the longer run to re-invent the wheel altogether and stop using ClickOnce.
Posted 13-Jan-12 2:25am

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 1

Go through this[^] discussion.

This[^] discusses another approach to achieve the same task.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web04 | 2.8.171020.1 | Last Updated 13 Jan 2012
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100