Questions about Organization|Installation Behavior options

[dbeukers]

I have an install that contains some files that are bitness-specific (and tied to the bitness of the installed version of Excel). I have a custom action to set a property for the Excel bitness. I would like to only install the appropriate ones for the install. I have 32-bit and 64-bit features, with the files correctly contained in each. I tried using the Installation Behavior fields to control this setting each feature to Installed, with a Not installed if: condition for the other bitness. That didn't work right, so I tried Not installed, with an Installed if: condition for the feature's bitness. In either case, I only get the 32-bit files installed, regardless of platform. What am I missing? The language in this section and the language in the Edit Conditional Levels dialog (from More Options in this section) is a little confusing to me, being somewhat new to install creation.

[Eusebiu]

Hi,

I'm not sure why your package does not install the features as expected. Can you please send me the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com, so I can investigate them and try to find the problem?

Best regards,
Eusebiu

[dbeukers]

The files have been sent as directed.

[dbeukers]

In light of your email, I see my error. I had overlooked the implications of the part about resolution of feature states in the Paths Resolution action. Moving my script to execute before Paths Resolution did resolve the issue.
As a side note, I had been able to make the install work as desired by using the same custom Bitness property (set *after* Paths Resolution) as a condition on the file, instead of the feature. Since this would affect required space, which is also calculated in Paths Resolution, the ability to change a file's install state after Paths Resolution seems improper.

[Eusebiu]

Hi,

I'm glad you got it working. Just let us know anytime you need help.

Best regards,
Eusebiu