You should probably use CAQuietExec rather than ExeCommand, that way the cmd
window doesn't pop-up during installation.
This is how I run batch commands in my installer:
<CustomAction Id="RunPostBatTask" BinaryKey="WixCA" DllEntry="CAQuietExec"
Execute="deferred" Return="ignore" Impersonate="no"/>
<CustomAction Id="RunPostBatTask_Cmd" Property="RunPostBatTask"
Value=""[SystemFolder]cmd.exe" /C
"[INSTALLLOCATION]Server\bin\post-install.bat""
Execute="immediate"
/>
You would have to call 2 custom actions though in the control element.
--Pavan
-----Original Message-----
From: wixard [mailto:amit.mo...@citrix.com]
Sent: Wednesday, March 26, 2014 3:51 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom action from ControlEvent fails
Thanks Pavan.
"Execute" is set to "immediate" if not specified. I explicitly set it to
"immediate". Still get the same error. Setting to "deferred" generates the
error:
DEBUG: Error 2762: Unable to schedule operation. The action must be scheduled
between InstallInitialize and InstallFinalize.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-action-from-ControlEvent-fails-tp7593782p7593785.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
