Dennis van der Stelt

Pingback from  Manual check for updates with ClickOnce - Dennis van der Stelt

Hi,

I was googling for a solution for the problem as described in the referenced article, concerning the "Launching Application" dialog.

Indeed, when un-checking the "The application should check for updates" check, the dialog is supressed until I call the CheckForDetailedUpdate() method in the ApplicationDeployment class. If I choose not to update the application, the dialog is back when restarting the application.

Is this a bug or am I missing something here?

However, nice walkthrough!!

Jeroen.

Hello Jeroen de Zeeuw, I've the same problem. It behaves like a bug.

Did you find a workaround?

Pingback from  turn off automatic update notifications

I struggled with this for a while before finally figuring out what was going on.  The CheckForUpdate() and CheckForDetailedUpdate() methods persist the results of the update check to disk.  The next time the application runs, the ClickOnce mechanism sees that an update is available and prompts the user with the unwanted window.  Apparantly the update is a two step process.  Step 1 - Check the deployment location for updates and persist the information about what it finds to the local ClickOnce update cache.  Step 2 - Check the local ClickOnce update cache and prompt the user with the update window if there an update is indicated.  Unchecking "The application should check for updates" option seems to only cause ClickOnce to skip step 1.  Step 2 still occurs.  The CheckForUpdate() and CheckForDetailedUpdate() methods have the same effect as step 1 - the data is persisted to disk, so the next time the application is run, Step 2 sees the update and displays the update window.  The trick is prevent CheckForUpdate() and CheckForDetailedUpdate() from persisting this information to disk.  This can be done by useing the parametered overload (CheckForDetailedUpdate(persistUpdateCheckResult)) and set the parameter to false (CheckForUpdate(false) or CheckForDetailedUpdate(false)).  The MSDN documentation for the persistUpdateCheckResult is weak at best and doesn't explain this at all.

@Joe - thank you for explaining that persistUpdateCheckResult parameter. You are right that the MSDN documentation is weak at best. Fortunately a Google search led me to your comment and that makes a lot more sense now!

Its really helpful to me...Please spread out this information...lot of people asking the same question in the internet.

I’ve written some tutorials in the past to help people with manually updating their ClickOnce deployed

What you said works, but i have another issue.  After all the check, when the actual update is happening and if the update fails because of network issues, next time when you open the application, the update window is coming again.

@Joe

Holy crap, thanks for pointing that out. This was driving me nuts.

Make your life time more simple take the <a href="http://bestfinance-blog.com">loan</a> and all you want.

We have the same problem with update dialog "Update/Skip" even with the "Check for updates" option unchecked.

We put the CheckForUpdates(False) lines at the beginning of our application (huge application) but it continues sending the dialog.

To find out where is the right place to put the lines, we put a messagebox right before this lines, but when we saw that first put the update dialog and then the messagebox.

Where I have to put it on? Is there a special generated code wrapping the application, and there is the right place to put the overload?

Desperate. Jose.

Thanks for the information. I had a problem with my unchecking of the "check for updates" box not being retained, enven though I did set an update location, as suggested. I found that I had to execute the publish process via the Publish Now button, using the wizard either from the publish page or from the menu caused the box to be automaticlly rechecked.