G
Guest
We would like to control the ClickOnce update (to see if the actual installed
version needs to be updated (customer dependent)), therefore we have
unchecked the “The application should check for updates†on the update page
under publish for the project properties.
But, if we, from our application, checks for a new update (by calling
ApplicationDeployment.CurrentDeployment.CheckForUpdateAsync() and ….) and
there is a new update, but we do not want to download it (the user says no,
or we do not offer the update). The application will offer the update next
time it is started (via the standard clickOnce update window).
Is there any way to turn of that check (which comes after we have checked
for a new version)?
Is it something with the deployment manifest – and can we change in the
manifest on the client (and where is it placed?)?
Can we simulate a click on the ‘skip’-button on the standard update window?
Regards
Bo Hauch
Jens Pontoppidan
version needs to be updated (customer dependent)), therefore we have
unchecked the “The application should check for updates†on the update page
under publish for the project properties.
But, if we, from our application, checks for a new update (by calling
ApplicationDeployment.CurrentDeployment.CheckForUpdateAsync() and ….) and
there is a new update, but we do not want to download it (the user says no,
or we do not offer the update). The application will offer the update next
time it is started (via the standard clickOnce update window).
Is there any way to turn of that check (which comes after we have checked
for a new version)?
Is it something with the deployment manifest – and can we change in the
manifest on the client (and where is it placed?)?
Can we simulate a click on the ‘skip’-button on the standard update window?
Regards
Bo Hauch
Jens Pontoppidan