Thank you for the link. I just find a way to avoid the problem: the ClickOnce system creates a key in the registry similar to it:
HKEY_CURRENT_USER\Software
and a binary value in it with a name like:
{2ad613da-6fdb-4671-af9e-1
this is the value that controls if the application should check or not for updates.
I'm attaching C# code to look recursively for the "PendingDeployment" substring at value names in the PackageMetadata key and then setting its value to two zero bytes to indicate that it should not look for updates.
Just call the NoManualUpdate() method after calls of CheckForDetailedUpdate() method and similars, and at DownloadFileGroupCompleted
Main Topics
Browse All Topics





by: nayernaguibPosted on 2008-03-25 at 08:03:02ID: 21202555
Looks like this is indeed a bug. It is reported on the following page:
sualStudio /feedback/ ViewFeedba ck.aspx?Fe edbackID=3 31132
http://connect.live.com/Vi
It might have something to do with publishing the application twice, as this is mentioned in the steps needed to reproduce the issue.
_______________
Nayer Naguib