How do I disregard an update?

I'm using the AutomaticUpdater control and I would like to have the option to disregard/ignore/not-process certain updates based on the version of the update.

I would like to be able to examine the version string of an available update and then have the option of completely ignoring the update to the point that the AutomaticUpdater reports the application is the latest version. I have some application users that are "testers" and I want them to be notified of every update and be able to download/install. The application "knows" if it is being run by a test user. I'm using a versioning scheme whereby the 3rd component of the version #, the 'release' in my [major].[minor].[release] version string, is used to identify test releases. In other words, for a regular user, if the major and minor versions are the same between the version they are running and the latest version available for download, I'd like to have availability of the newer version completely hidden from them.

I suspect there is some event of the AutomaticUpdater that fires after the availability of a new version is detected in which I can do something that essentially masks the detection of the new version.

I tried the easy thing -- did my test in the UpdateAvailable event and invoked the Cancel method. That didn't work.

Any suggestions?

There's no good way to skip updates using the AutomaticUpdater. (You can use wyUpdate in standalone mode).

I have some application users that are "testers" and I want them to be notified of every update and be able to download/install. The application "knows" if it is being run by a test user.

The best way to do that (currently) is to release separate *.wys files. Have the "testers" point to the latest *.wys on your server. Have your regular users point to a *.wys file that's only updated when you release a new stable version.

Does that make sense?

Thanks Sam.

It does make sense, but I was hoping to have a much simpler build process whereby I could hide test releases from regular program users simply by how I controlled the version information while still using the AutomaticUpdater control. I figured there had to be some event that got fired when a new update was available within which I could compare the version of the new update against the current version of app and simply set a cancel flag if I didn't want to process the update. This seems like such a useful feature and doesn't seem overly complicated to implement which is why I figured it probably existed. Oh well. Again, thanks Sam for your response.

Tom