views:

253

answers:

2

Hello,

I have a C# application (WinForms) (ClickOnce) whose repository is installed on a server that is about to crash, so my boss asked me to move the repository, but there are around 300 client machines which have the application installed.

The ClickOnce is signed with a Test Certificate.

Is it possible to move the repository without having to reinstall in the client machines?

Thanks in Advance

[EDIT]

I Have published the application to the new server, but the clients don't reach it, what else can I do? I think i should change something inside the manifest or something like that, but a actually don't know too much about ClickOnce... In any case, i would like to avoid the reinstallation on all the client machines, any ideas, suggestion? thanks in advance

+1  A: 

You could try to change the DNS alias so that it redirects to your new server.

The fact that the code signed using a certificate is not relevant, since code-signing certificates are not bound to a specific repository (as opposed to SSL certificates)

Btw, why don't you want to reinstall? The whole point of clickonce is to ease this kind of software update !!

Brann
But i actually need to move the repository, the movement is planned and the server currently hosts other applications so i would say i don't have control over the server.
Jhonny D. Cano -Leftware-
If the server is about to crash, why not replacing it totally by a new one with the same dns name? In case you're not in a position to take that decision, you may want to redirect your repository URL to another server
Brann
The reinstall via clickonce is usually automatic, we fear that, when we change the repository url, that oblies us to reinstall on every machine.
Jhonny D. Cano -Leftware-
Definitely not. just change your clickonce application so that it uses another repository (ie the new one). really, I think you're overcomplicating your situation. deploying a new version on the old repository targeting the new repository as the install repository WILL work
Brann
A: 

Here is what I have done, for people who may have the same issue.

  • Setup the new server on the publish package. (Project Properties, Publish Tab)
  • Publish to the new server
  • Copy the published files to the old server. (Include the .application file and the folder)

When the clients reach the old server, they will update, but the server location will be updated on the client to the new server name.

Jhonny D. Cano -Leftware-