If you run silently from the command line, the UI sequence is not processed
at all, it goes straight to InstallExecuteSequence.
Therefore, if you have any custom actions that will dictate what gets
installed, you need to ensure that they are scheduled in
InstallExecuteSequence, instead of or in addition to being scheduled in
InstallUISequence. If the action won't work properly if run twice, set
CustomAction/@Execute="firstSequence" so that it runs in either the UI
sequence, if UI is enabled (/qf or /qr) or in the Execute sequence, if not
(/qb or /qn).
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Menaker
Sent: 26 July 2007 20:22
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Problems when running installer silently from
commandline
What are possible issues with running an installer silently from the
commandline:
MSIEXEC /i MyInstaller.msi /Log LOGFILE.TXT /qn ADDLOCAL=AllMyVariables
This works for almost the entire installer. However, it has a problems with
an internal property that is set on a UI page (it doesn't get evaluated even
though it is defaulted to false and should install something).
And another is a component that doesn't rely on anything but for reason the
files don't get copied and the registry is unchanged.
Is there any known issues from the installer?
BTW I'm using WiX 2.0
Thanks,
Mike
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
