Last Updated
Viewed 05 Times

We're adding aliases to the servers that are currently hosting our ClickOnce deployments for our WinForms applications and want to point the deployment to use the new alias (e.g. moving from //servername/appname/app.application to //applications/appname/app.application). This is due to the fact that we are planning on retiring our current servers and hope to make future migrations between servers easier. Ideally, we want to not require users to un/reinstall the affected applications.

Would it be as simple as changing the Installation Folder URL and Update Location to use this new alias or would this possibly be more complicated? Happy to answer any questions for clarification.

I have a collection of ClickOnce packages in a publish folder on a network drive and need to move them all to another server (our DR machine).

After copy/pasting the whole directory and running the setups on the new machine I get an error message stating that it cannot find the old path:

Activation of ...MyClickOnceApp.application resulted in exception. Following failure messages were detected:

+ Downloading file://oldMachine/c$/MyClickOnceApp.application did not succeed.

+ Could not find a part of the path '\\oldMachine\c$\MyClickOnceApp.application'.

Once I change the installation URL to point at my new machine, I get another error:

Manifest XML signature is not valid.

+ The digital signature of the object did not verify.

I've tried using MageUI.exe, to modify the deployment URL, but it asks for a certificate, which I don't have.

What am I doing wrong and how do I successfully move published ClickOnce packages?

In my project i have 85 mb files, out of which 70 mb files are Third party control dlls which dont change often, and remain 15 mb are my application files.

When i publish the project, it is uploading all the files (85 MB) and hence taking around two hours to publish to the server.

Is there any way that i can just publish the exe and application files and then copy the remaining dlls manually to the server


the dlls must be copied to client machines from a specific location?

What should i do to speed up the publish?

From the sounds of this StackOverflow answer it seems that when I publish my app for our company to use internally I have to manually remove the older "versions" from [Publish Directory]\Application Files.

I'm assuming this is correct, but is there any consequence to doing this? I've read that ClickOnce does merging changes to application settings, but does it need the other versions for patching an upgrading app?

I'm concerned about the scenario where I have a user that has skipped upgrading for a version or two and when they do decide to upgrade the ClickOnce architecture requires that the deployment folder contain all the versions and the current most deployed version in order to upgrade.

This doesn't seem plausable to me, but can someone confirm that all I need in the folder is the latest version? Also, any help in writing a Windows task to clean out all the older versions except the most recent would be very helpful!

Similar Question 4 (1 solutions) : How to force ClickOnce deployment url?

Similar Question 9 (1 solutions) : clickonce deployment