The individual property values should be in the log if it's verbose.
If they don't appear that typically means they are not being set at
all.
I've used a debug dialog in similar situations. At the end of the UI
sequence have a dialog that's just a display of the property values
you're interested
Say I have a complex boolean expression in, for example, a component condition
and it’s not evaluating how I expect. Is there any way to get Windows Installer
to ‘echo’ the condition variables as evaluated at install time as an aid to
debugging. For example maybe I used (Property1=1) Or
2 matches
Mail list logo
