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.
FOLLOW US
Get the latest news in Application Packaging