As promised, here is my followup to this issue.
It seems that, without the EUI, the setup can not pass the property to the MSI.
I can not say for sure if this is a bug or simply a corner case which our development team did not consider.
To work this around, you can declare the property in "Properties"
page and give it a value, e.g.:
After doing so, however, the condition you currently use for your custom action will always be true, i.e.: TEMP_VAR2
, because this basically means "execute the custom action if TEMP_VAR2 property exists" and, since we defined it, the custom action will always be executed.
To avoid this, we will need to be a little bit more specific with our condition, e.g.:
This way, we will always execute the custom action if the property is "0" (meaning that the prerequisite was installed).
I have also forwarded this scenario to our development team so we can further investigate this and try to find a solution.
I will update this thread as soon as this will be fixed.
Hope the workaround will help!