Update ClickOnce Version by Replacing Deployment Files with New Build Files files


how do we update the clickonce clients?

Right now we have clickonce packages on a server xxx.yyy/customer/clickonce/ClickOnceDeploymentFiles/ …

We know we need to make the new client files available, So that when the User open his ClickOnce the Client will be updates to the new Version. but how?
What I tried till now (2 different ways):
First Way:

  • I replaced the …/Deployment/Applicationsfiles folder with the neu CU deployment Files. But I didn’t replace the manifest!
  • I also updated the manifest version No. with the new Bulid no.
  • Also I made the required minim version to be

When the user open his click once is starts normally & nothing happens pastedimage1512644633248v3.png

Second Way:
I made a new installation for the new Bulid + I renamed the new Folder to have the same name like the old deployment folder + I deleted the old Deployment folder!
When the user open his click once it gave back an error & it cannot start the client, I have to install ClickOnce then it will work! → I want to avoid this

So can anyone tell me please how can I make Clickone to update it self once the user open it? We have almost 50 user which uses clickonce, I donot want to make a new deployment! coz if i did so i have to deinstall the old client and reinstall the new client on 50 Pcs.

Once they install ClickOnce they have the config file information into there local PC. So just changing the build wont gonna help. Manifest file is the key which contains the entire information. I know its painful to uninstall and reinstall the once click Application Manifest but if you really want to update this then I will suggest to go with this option only as this wont gonna take much time. If you go on changing modifying the existing one you will end up with doing just hit and trials, but this one might sounds crazy doing but for me its the best option with less time.

If users are really laymen and they even dont know how to uninstall and install a software then you can go ahed with your hit and trials and all.

Hi RockWithNAv,
Thank You for your message. But I am really sure there is a way to Update the Client without uninstalling it & then reinstalling it :(.
I did it in the past one time & know I canot remember how I did it.

Update Steps -----> I managed it :slight_smile:

Phase 1 (New installation CU xx):

  • Make new installation/Deployment Folder with name CU XX

Phase 2 (Update Old installation):

  • Copy all files from Deployment folder (From New CUxx) EXCEPT!! (Config Files Datei)
  • Past the File in the Old installation deployment folder!

Phase 3 (Submainfest):

  • !!!Start Mageui as ADMINSTRATOR!!!

  • Modify the Sub-mainfest Version to = “new version Code 9.0.0.xxx”

  • Load the New Files a gain in the MainFest

  • Save & Close the SubMainfest

Phase 4 (Mainfest):

  • Modify the main Mainfest
    . Version = New version No.
    . Least version = New version Code
    . Load the Submainfest Files again

  • Safe the certificates!

  • Start Your Cliernt


Yep I know there’s always a way but in a nutshell it was a generic recommendation for click once so that eventually you dint end up with a lot of time wasted, if in 1 go or 2 you are successful then it’s fine otherwise that’s the approach which normally I follow on this.