Previous Topic: Product DeletionNext Topic: SXP Product Version Registration

Using the Packager for Windows › SXP Product Conversion to MSI Product

SXP Product Conversion to MSI Product

After you have completed packaging an SXP product using the automatic method, you can optionally convert it to a software product in the Microsoft Installer (MSI) packaging format. The converted MSI product is stored in the product archive with the same version number expanded by .msi.

Converted MSI products are registered in the Software Package Library and installed on target computers, as SXP products are.

During the SXP to MSI conversion, all files are added to a single .cab file in the MSI package. The maximum size of a single .cab file is 2 GB. This means that SXP packages larger than 2 GB cannot be converted by the SXP to MSI Converter.

During installation of an MSI product the Microsoft Installer sets properties. Default values for the properties are predefined in the MSI product in the Property table. Each package contains a minimum set of properties. Some of these properties are reserved and must not be changed, for instance, ProductCode, whereas others may be customized, for instance, REBOOTPROMPT.

When converting an SXP product to an MSI product, SXP parameters are mapped to MSI properties. For each external (client) parameter found in the SXP product, a public property with a default value is created in the property table. The values are taken from the sxpparam.ini file, if an appropriate entry exists. Otherwise, the property value is set to Undefined, and the user must specify a default value. Some internal parameters are not automatically mapped to MSI properties and therefore must be edited by the user.

Because the MSI format does not support all SXP features, there are restrictions for the SXP to MSI conversion. For example, in SXP formatted files any user-specific item can be configured for installation for one or multiple users or groups, and flexible assignment of users and groups is provided. Because this behavior is not supported by MSI, any user-specific object will be installed for all users.

Any problems during conversion, such as restrictions detected, are listed in the file Comment.txt, which is created in the MSI product directory. In the terminating message the user is informed about the entries in the Comment.txt.