Hi Mike,
Thank you for the answer; but I think the property is in the same file; this
is the XML sequence which works fine in the .MSI:
"<CustomAction Id="CAPCInstall.Command" Property="QtExecCmdLine"
Value=""[INSTALLDIR]AppSecInc.Performance.CAInstaller.exe""/>
<CustomAction Id="CAPCInstall" BinaryKey="wixca" DllEntry="CAQuietExec"
Execute="immediate" Return="check" />
<Binary Id="wixca" SourceFile="$(var.WIX_DIR)\wixca.dll" />
<CustomAction Id="CAPCUnInstall.Command" Property="QtExecCmdLine"
Value=""[INSTALLDIR]AppSecInc.Performance.CAInstaller.exe" 1"/>
<CustomAction Id="CAPCUnInstall" BinaryKey="wixca" DllEntry="CAQuietExec"
Execute="immediate" Return="check"/>
<InstallExecuteSequence>
<Custom Action="CAPCInstall.Command"
After="RegisterProduct"></Custom>
<Custom Action="CAPCInstall"
After="CAPCInstall.Command"></Custom>
<Custom Action="CAPCUnInstall.Command"
Before="RegisterProduct">Installed</Custom>
<Custom Action="CAPCUnInstall"
After="CAPCUnInstall.Command">Installed</Custom>
</InstallExecuteSequence>"
Do you think I forgot to add something, or is there anything to do with
[INSTALLDIR], and how the WIX replaces the [INSTALLDIR] string?
I also hardcoded the EXE path in the .MSM file (in "Value") and I am getting
the same error. My WIX version is 3.0.
Thank you,
Elena
_____
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: 2007-Oct-29 Mon 5:57 PM
To: 'Elena Diaconu'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Custom actions launched from .MSM files
Deferred custom actions get their instructions on what to do from a property
named the same as the custom action itself, which in the CA code itself is
the CustomActionData property.
When you include something in a module, by default its identifier is
modularized, that is, a GUID is added after the identifier you specify. This
is to prevent name clashes between different modules and between a module
and the installer.
I'm guessing that the custom action itself is being modularized - you can
see this below - but the property isn't, or the property is in a different
module to the CA.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Elena Diaconu
Sent: 29 October 2007 16:05
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom actions launched from .MSM files
Dear WIX users,
I have a problem when I am trying to launch an executable through a Custom
Action from an .MSM file: the WIX installation fails.
When the executable is launched from an .MSI file everything works fine. So
is launching executables through Custom Actions from .MSM files supposed to
work or not?
Below it is the errors log sequence:
"MSI (s) (1C:58) [18:03:58:968]: Doing action:
QtExec.412198FF_0AE9_4CB8_889D_53756DDAC731
Action 18:03:58: QtExec.412198FF_0AE9_4CB8_889D_53756DDAC731.
Action start 18:03:58: QtExec.412198FF_0AE9_4CB8_889D_53756DDAC731.
MSI (s) (1C:A0) [18:03:58:984]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSIADF.tmp, Entrypoint: CAQuietExec
CAQuietExec: Error 0x80070057: failed to get command line data
CAQuietExec: Error 0x80070057: failed to get Command Line
Action ended 18:03:59: QtExec.412198FF_0AE9_4CB8_889D_53756DDAC731. Return
value 3.
Action ended 18:03:59: INSTALL. Return value 3."
Thank you, I appreciate your answer(s),
Elena
Elena Diaconu
Sr. Software Engineer,
Application Security Inc.
appsecinc.com <http://www.appsecinc.com/>
-------------------------------------------------------------------------
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
