Dear Advanced Installer Support Team,
I have a feeling custom action conditions are not working 100% correct, there might be a big in that area. We use Advanced Installer 14.5.1.
We have a custom action called DiscoverFirewallRules(powershell inline script) which is doing the following: it´s changing a value of a property from 0 to 1. For testing purposes I wanted to disable this custom action of ours by settings its condition to "FALSE" (I also tried to insert 0 into the Condition textbox).
The interesting thing is that in the installation log (L*Vx) file contains the name of our custom action in 6 places:
- the content of the whole powershell script appears in the log
- "MSI (s) (58:C8) [10:14:58:308]: Doing action: DiscoverFirewallRules"
- "Action 10:14:58: DiscoverFirewallRules."
- "Action start 10:14:58: DiscoverFirewallRules."
- "Action ended 10:15:07: DiscoverFirewallRules. Return value 1."
- "MSI (s) (58:88) [10:15:48:088]: Skipping action: DiscoverFirewallRules (condition is false)"
The last occurrence would suggest that the custom action was not running, but actually it was, because our property´s value has been modified from 0 to 1.
My question is: Why "FALSE" and "0" conditions are not turning off a custom action? That would be logical. Is it a bug in Advanced Installer.
For reproduction:
1. Create an "inline powershell script" custom action which is changing a property. For example contains a line like this: AI_SetMsiProperty YOUR_PROPERTY 1
2. Set its condition to FALSE or use 0
3. Install it on a PC from Command Line tool by using "L*Vx logfile.log" param
4. Analyze the log file -> confirm that the custom action was executed
Could you please try to reproduce this issue? Thanks in advance!
Best regards,
Zsolt