Gradual release for advanced installer updater

[alter_ego_dev2]

I would like to have the possibility to release updates to smaller groups of users to check that app doesn't have issues without bug risks.

It is up to you how to implement the mechanism. Here is a simple example of possible logic:
An additional property in updateConfig.txt files (for example, version 2.0.0 updateUserPart = 20%), the client app on install could generate a random number from 1 to 100 and save as updaterGroup (for example updaterGroup=15). In this case, updater app could check, if updaterGroup is smaller than updateUserPart (15 < 20) then the app installs version 2.0.0 Another user with updaterGroup=30 doesn't get version 2.0.0 and should wait until the release would not change updateUserPart to bigger number (up to 100%).

[Catalin]

Hello,

I have added this on our TODO list of improvements and hopefully it will be added in a future version of Advanced Installer.

Thank you for bringing this to our attention!

Best regards,
Catalin

[Catalin]

Hello,

After further consideration, we might have a workaround here that I would like to get your opinion on.

You can call the updater from within your application. You can generate the number from the application, or have a script generate the number during installation and save it in the registry.

The application can then check this registry value and, based on it, decide whether to launch the updater to check for updates.

How does this sound for you?

Best regards,
Catalin