Installer conditions don't seem to affect custom action

[chriserickson]

Hi,
I have a custom action which runs the install util on a library that is installed. For it to succeed, a 3rd party library needs to be there. I'm using the following as an execution stage condition:

VersionNT64 AND ARCGIS_VERSION >< "10."

It appears to run every time, even though the ARCGIS_VERSION variable shoudl be 'null'.

Help?

[mihai.petcu]

Hello,

The condition should resolve to TRUE if you are installing on a 64-bit machine and the ARCGIS_VERSION public property contains the string "10.".

You can watch the value of the property by displaying it in a message box before the custom action runs.

All the best,
Mihai

[chriserickson]

Thanks!
I may be missing it, but how do I display a variable in the message box text?

[mihai.petcu]

You're welcome.

Just follow the inline link from my previous post (blue text). The "Message Box" custom action's action data field is formatted type so you can easily reference public properties.

All the best,
Mihai

[chriserickson]

Ok, I've verified that in this case ARCGIS_INSTALLER is not set to anything. Am I doing something wrong with my condition?

[Daniel]

Hi,

I'm not sure why you are encountering this behavior. Can you please send us your .AIP (project) file and a verbose log of the installation package to support at advancedinstaller dot com so we can investigate them?

Regards,
Daniel

[Bogdan]

In the log sent by e-mail you can find this at line 1524, Skipping action: Arc10Extension_64 (condition is false). This shows the custom action is not going to be executed because the condition is false.

Maybe you are confusing the custom action with another one from the package, as I see you have difference execution conditions for all of them.

Regards,
Bogdan

[chriserickson]

I had assumed that a custom action was automatically excluded when its underlying component was excluded. This isn't the case, and was causing my problem.

Thanks for the awesome support!