sorry for the delayed response...i just realized that my email address was out of date.
Under the "Cusom action and sequences" view, expand the "Installation\User Interface" tree. For each dialog node set the condition to "0", or simply remove it from the sequence altogether (i'd recommend setting the condition to "0" at least until you've tested the whole thing), or set it to a condition based on something settable from the command line (if that's what you'd like.)
This is not typical in installations because we usually want to present at least one dialog when a setup exe is clicked...just in case the user happens to click it accidentally. In this case, you'll probably want to use the InstallWelcome dialog or the ReadyToInstall dialog. Then just modify it so that it makes sense to the user. Alternatively, you could probably schedule a Set A Property CA that will set [UILevel] = 3 prior to any unwanted dlgs.
As per help (also I tried) CA can’t set the UI level,
snippet from help; You should use the UILevel property to determine the current user interface level. You cannot call MsiSetInternalUI from a custom action and it is not possible to change the UI level property from within a custom action.
Thanks for the tip LP! Learn something new everyday 😮 I thought i'd done this is an earlier project, but i was really just setting a public property to the initial value of UILevel since the actual value of UILevel was changing between the UI and EXE seqences, and blah blah blah... I'll stop justifying my existence, now.
Glad i provided at least one solution that would work. :cool:
