Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 4

Anyway to set the default on components to x64-Bit Component

It's really annoying to have to change it for 300 components after they have been added. The warning message I am getting is this one:

ISDEV : warning -7143: Component utf8_and_euc_jp.dll installs to a 64-bit folder but is not marked as a 64-bit component. This may result in an incorrect installation path for this component's files.
Labels (1)
0 Kudos
(2) Replies
Level 6

Plus 1

I too would like to see this.
0 Kudos
Level 17

To change the attributes of your existing components, you can use the ISWiComponent automation interface object. Set the Attrib64BitComponent property to True to have a component registered as 64-bit. If you want to create new 64-bit components automatically, you may want to consider evaluating the new ability introduced in InstallShield 2016 that enables you set the default value used for component attributes. Here is the description from the InstallShield 2016 Release Notes:

Ability to Set the Default Value Used for Component Attributes
Support for a new property has been added to the InstallShield table that lets you set the default value used for component attributes. If a property of MsiComponentAttributes exists in the InstallShield table, its value overrides the default Attributes column value in the Component table from 8 to whatever is specified.

For example, to make new components 64-bit, add 256 to the MsiComponentAttributes value. You can specify 264 (for 64-bit shared) or optionally enter 256 (for 64-bit unshared). In doing so, the 64-Bit Component setting and Shared settings (shown on the in the General area of the Components view) will be updated to Yes or No accordingly.

For more information about the bit values used in calculating the Attributes column of the Component table, refer to the Component Table page in the MSDN Library.

Note: To set the default value used for component attributes, the MsiComponentAttributes property must be updated manually in the InstallShield table in the Direct Editor of each project. The Template Summary setting for a product configuration is ignored for this use case.
0 Kudos