I have a custom action with the Condition - Not Installed And (Not DETECTED_PROD)
During the first time install the custom action was not triggered because the DETECTED_PROD property was found. This is what I expected, but then when I run the install again in maintenance mode I would not expect this custom action to be triggered because: Not Installed would now be false, but for some reason it triggered.
So where in the sequence is the Not Installed/Installed states get set. Maybe I am calling the custom action too soon and therefore the properties are not set yet?
Installed Property should have been initialized well before hitting the first (standard/custom) action. Is it possible it was installed for a different user?
