Detecting Installed Earlier Versions that Need to Be Updated

InstallAnywhere 2017

Edition • The Premier edition of InstallAnywhere includes support for creating upgrades that update earlier versions of a product.

When you are configuring the upgrade settings in your project, you need to specify details about the earlier version or versions of your product that you want to be able to update with the upgrade that you are creating.

To define which earlier version or versions of your product need to be updated:

1. In the Advanced Designer, on the Project page, click Upgrades. The Upgrades view opens.
2. Find the Upgrade Configuration setting.
3. In the Upgrade Configuration setting, click the Manage Upgrade Configurations button.The Manage Upgrade Configurations dialog box opens.
4. Use the List of Upgrade Configurations box to define one or more configurations that specify how your upgrade should detect earlier versions of the product that need to be updated.

By default, this list shows a Default Upgrade Configuration item.

Perform each of the following tasks as needed:

To add a new configuration, click the Add button next to the list.
To view or edit the settings for a particular configuration, select the configuration and then review and modify the settings below the list as needed.
To remove an existing configuration, select it in the list, and then click the Delete button.
5. Configure the settings in the Criterion for Detecting Which Products to Upgrade area and the Range of Product Versions to Upgrade area as needed.
6. Click the OK button.

For more information, see Manage Upgrade Configurations Dialog Box.

If upgrade support is enabled in your installer, the installer checks the InstallAnywhere registry on target systems for one or more earlier versions of the product that meet the upgrade configuration conditions that you configured on the Manage Upgrade Configurations dialog box.

Tips on Specifying Details about the Earlier Versions of Your Product

Upgrades that are built in InstallAnywhere need to be able to identify earlier versions of the product that are present on target systems and that are eligible to be updated. You can specify these sorts of details by defining one or more upgrade configurations in your project. An upgrade configuration consists of two main types of data:

Managing Upgrade Configurations

Criteria

Notes

Upgrade code or product code

The upgrade code should be consistent across different versions and languages of a family of related products. For this reason, this identifier is often preferred rather than the product code for detecting earlier versions.

The product code is sometimes updated for new versions of a product; in other scenarios, it is kept the same across versions. If you want to use the product code instead of the upgrade code for detecting earlier versions, you can specify whether you want to check for the product code that matches the one in the current project, or you can specify the specific product code from an earlier version of the product.

Note that if the base installer was created in a version of InstallAnywhere that did not include an upgrade code (that is, if the base installer was created in InstallAnywhere 2013 or earlier), use the product code for detecting that earlier version.

Range of product versions

The version number for the upgrade must be higher than the version number of any of the base versions. That is, the version that you specify in the General Settings view of the project must be higher than the range that you specify for the upgrade configuration.

To target a specific earlier version of your product, you can enter the same version number for the minimum and maximum version numbers.

Thus, depending on whether each earlier version of your product has an upgrade code or uses the same or a different product code, you may want to define multiple upgrade configurations on the Manage Upgrade Configurations dialog box.

The following table shows sample upgrade configurations for upgrading to version 5.0.0 of a product. The upgrade is intended to target all of the earlier versions of the product; that is, if any of the earlier versions of the product are present, the upgrade has support for detecting these earlier versions and uninstalling them before installing the new version.

Example Upgrade Configurations for an Upgrade Installer

Upgrade Configuration

Detection Criterion

Product Version Range

Default Upgrade Configuration

The installer for this version of the product did not have an upgrade code.

Different product code than that of the current project

1.0.0–1.99.999

Upgrade Configuration 1

The installer for this version of the product did not have an upgrade code. However, the same product code has been used for this version and all of the newer versions of the product.

Same product code that is in the current project

2.0.0–2.99.999

Upgrade Configuration 2

The installer for this version of the product had an upgrade code.

Same upgrade code that is in the current project

3.0.0–4.99.999

See Also