Hi Brian,

When an update is created we have to provide the location to retrieve the update from. All applications will always check this location.  If I want to test an update prior to release it, is there a way for me to control where to download the update from? also how could this be done?

Basically I want to be able to test an update before allowing the customer to download the test update.

Hello Edhy,

The solution is to utilize the Custom Data property of an update.  Here you can add any value you like during the publish process, and remove or alter the value from the Manage Publlished Updates window without rebuilding the update.

You will add a string value such as "Test=true" or simply "test update" when you publish the update.  Then in your code, you can access this value from the CurrentUpdate property after a check for updates process completes.  If your own application setting that controls whether or not to allow test updates is not set, then check the custom data for an indication that the current update is a test update.  If it is, set the current update to null, effectively hiding the update.

Alternatively you could utilize the UpdateFound event of the update controller to perfrom the test update check. You'd do the same thing, except set the e.SelectedUpdate to null, or the highest available non-test update in the e.AvailableUpdates collection.

Hello Edhy,

If you used the solution I described, you would no longer use the tester/limited key in an app.config. file.  Instead of  using the test update checkbox, you'd identify the update as a test update by using the custom data field, and rely on your application code to control the visibility of test updates to your clients.  It would work for you and it is the only way to accomplish your goal with the currently released software.

I'll add to the feature request list a new update controller property to control test update behavior.  This could enhance the built in test update feature. The benefit of the app.config approach is that no previous code or code changes are necessary to configure a tester installation. Install your application onto a client and add/modify the config file for testing updates.