I am using ClickOnce to deploy a VB.Net 2005 application. It all works
well, but I have a question about how ClickOnce works.

If a newer version of the application is available and a user chooses
to "Skip" installing it, they don't ever get asked again. Is this the
designed behaviour of ClickOnce? How do I get the user to see a prompt
for a newer version again? Do I need to publish another version with a
publish number greater than the one that they have skipped, or is
there a configuration file that I can tweak so that the user gets
prompted a second time for the version they already skipped?

Yes, that is the designed behavior of ClickOnce. You have to publish a new 
version for the user to pick it up.

ClickOnce has a programming API. You could add a "check for updates" option 
to your menu, and call it to do updates as well. That's as much as I know 
about that -- check out Brian Noyes' book on ClickOnce deployment for more 
info.

Good luck.
Robin S.
---------------------------------------
 wrote in message 
news:1185471517.862626.265490@x40g2000prg.googlegroups.com...

>I am using ClickOnce to deploy a VB.Net 2005 application. It all works
> well, but I have a question about how ClickOnce works.
>
> If a newer version of the application is available and a user chooses
> to "Skip" installing it, they don't ever get asked again. Is this the
> designed behaviour of ClickOnce? How do I get the user to see a prompt
> for a newer version again? Do I need to publish another version with a
> publish number greater than the one that they have skipped, or is
> there a configuration file that I can tweak so that the user gets
> prompted a second time for the version they already skipped?
>