How can I avoid this behavior and configure the application to never checks for new updates automatic.
Just want to ask you a question:
Did you figure it out
If yes please post the solution here.
I'm doing the same and facing the same problem. :-(
Unfortunately, no.
We think that it¡¯s a bug in ClickOnce technology
What we did was to change the deployment process, we moved to a simple windows installer and we have a xml in a web server that provides the necessary information to know if a new version is available, if it¡¯s we execute a process that runs the setup from a share drive; we uninstall the current version using msiexec /x [package name] /passive and then install the application.
It¡¯s an easy option and you just need some hours to do it.
Key parts:
Read a XML from a url
Parse the XML to a custom object
Verify app¡¯s version
Some backup (optional)
Uninstall the application
Install the new version from a share drive.
I hope that this will be useful for you.In the Publish settings, the Updates dialog, you should be able to set the application to Never check for updates. It's the topmost checkbox. Then, your application will rely on your use of System.Deployment (or My.Application.Deployment) to check and download updates.
Yepp
Thanks a lot.
I've got the same problem.Before I read this thread it drive me crazy.Does anyone know how to walkthrough it
Has anyone found a workable solution to this problem, or even got any acknowledgement from Microsoft that the problem exists
(Note there is a similar post here: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=562713&SiteID=1, where a number of other people are having the same issue.)
hi all,
I have the same problem you describe.
Do you know if there are news from Microsoft Developement Team about this bug
Thank you.
Paolo
Hi Guys
I am in the same boat, i think.
I haven't created a custom update yet, i have played around with the auto update and set it to 365 days, i checked for an update and then cancelled. When i restarted the app automatically checked for the update. Future checks were only made after the 365 days had expired. So what i have experienced id that it only checked for an update once after cancelling and then on schedule afterwards (365 days)
With the custom updates, does it only check the once after cancelling or does it look for updates every single time after cancelling
I need control over the updates as they are subscription based, my initial thought would be to use a web service, with the current software version on my server database, to see if a newer version was available and if so and the user wanted to install, then call the update method, this way it would give me the update ability with clickonce.
Any ideas
Regards
Steve
I have created a custom update, after checking for an update and not accepting, when i restart it automatically checks for the update and prompts again. After issuing another update, i do not get an automatic prompt unless i cancel again. Are you guys experiencing the same i.e. only 1 check for an update after cancelling then returning to the custom setting
Rgds
Steve