Some public MSI properties not passed to execute sequence when using Enhanced UI - Advanced Installer Community
sbaird
Posts: 57
Joined: Tue Sep 01, 2015 2:08 pm

Some public MSI properties not passed to execute sequence when using Enhanced UI

I noticed that when using the Enhanced UI, only certain MSI properties are passed from the UI sequence to the execute sequence. It seems that only properties which are either specified on the command line, entered into the Property table, or associated with a UI control are passed. If a public property is added/set via custom action in the UI sequence, its value is not passed to the execute sequence. This violates the Windows Installer specification, and I have confirmed that the behavior works as expected when using an MSI-based setup.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Some public MSI properties not passed to execute sequence when using Enhanced UI

Hello,

Indeed, this is an Advanced Installer issue specific only to our "Enhanced User Interface" feature. We apologize for the inconvenience. We will investigate this and will try to add a fix for it in a future version of Advanced Installer.

Until then, as a workaround, you can go to "Install Parameters" page and also add your public property in the "Properties" section from there.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
sbaird
Posts: 57
Joined: Tue Sep 01, 2015 2:08 pm

Re: Some public MSI properties not passed to execute sequence when using Enhanced UI

Thanks for your quick response.
Until then, as a workaround, you can go to "Install Parameters" page and also add your public property in the "Properties" section from there.
This would work for many cases. However, in my case, I have a property which I need to check if the user has defined on the command line. If the property exists in the Property table, then it must have a default value, and I cannot know if the user has set it. If the user does not set it on the command line, then I use a custom action to give it a default value. The reason I need to be able to distinguish these cases is that if the user specifies the property, then there are other validation rules for other specified properties which have to be checked. I have worked around this issue by associating the property in question with a hidden UI control, which causes it to get passed to the execute sequence.

Return to “Common Problems”