Managing multiple versions

[bvelke]

I make a retail product with thousands of users. When we release an update, we increment the second number in the product version string (8.00.0000 vs 8.01.0000) and we release a full installer (not a patch) with the Advanced Updater. In this case, we want it to upgrade their current installation, not install a second copy.

We use the third number in the product version string for beta releases (8.00.0000 vs 8.00.0042). We want beta testers to be able to preserve their installation of the public release and have a second installation for beta testing.

I thought that I understood this. With each release (beta or public), we update the Product Details > Product Version field and specify that it is a major update to generate a new Product Code. Upgrades > Application Versions is set to "Allow side-by-side installs of different product versions".

While this seems to work for beta testers and first-time installers, it is a problem for real users who have an earlier version installed. First, that latter group is prompted for the installation folder and we'd rather they weren't. More seriously, some users have managed to get two installations in the SAME folder - and I really don't know how that's possible.

What am I doing wrong?

[mihai.petcu]

Hello,

Upgrades > Application Versions is set to "Allow side-by-side installs of different product versions".

By your concerns and current settings I believe you missed our user guide upgrade settings' reference and implementation steps:
http://www.advancedinstaller.com/user-g ... rades.html
We recommend you read both "Automatically upgrade older product versions" and "Allow side by side installs of different product versions" sections of the above article. This way you'll be clarified and know each setting's behavior to decide the one that best suits your needs.

You may also find this article relevant.

After re-evaluating your future upgrade strategy, let us know if you have any questions.

All the best,
Mihai