Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a ClickOnce deployment for a specific application with many existing users. Currently, the deployment manifest specifies “auto update on startup” option.
I would like to change the deployment manifest so it would specify that auto update is turned off and I could manually trigger update for my application.
What bothers me is the question if current deployment can be updated without users reinstalling the application.
The answer: yes, switching auto update off in the manifest does not break existing client installations, manual update strategy can be used afterwards and no reinstall is required.
(at least that worked with .NET 4.0 clickonce deployed application)