I seem to have found a bug with the 'SetPackageType' command. When 'SetPackageType' is called with the value 'x86', the resulting MSI does not install on either a 32-bit or 64-bit system (tested on Win7) and gives the following Windows Installer error : « This installation package is not supported by this processor type. Contact your product vendor.”
By default, the 'Package Type' field is set to '32-bit package' in the UI. After using the command, it still shows the same value, but when I look at the .aip file in a text editor, the following has been added:
<ROW BuildKey="DefaultBuild" BuildName="DefaultBuild" BuildOrder="1" BuildType="0" Languages="en" InstallationType="4" UseLargeSchema="true" MsiPackageType="x86"/>
I also analyzed the resulting MSIs in Orca and the following value differs:
Property->AI_PACKAGE_TYPE
- 'Intel' : Value when not using SetPackageType
- 'x86' : Value when SetPackageType is used
This is not a showstopper for us since the only thing we have to do is not use the 'SetPackageType' command when we want a 32-bit package type, but I felt it would be good to report it nonetheless.
Thank you,
Eric
FOLLOW US
Get the latest news in Application Packaging