Essentially, I added the cli argument in order to workaround the need for "Working Directory"...
After a little more investigation, it seems that a type 50 CA is what I need...
<CustomAction Id='LaunchConfig' Directory ='INSTALLDIR' ExeCommand='[INSTALLDIR]$(var.projectname).exe' Return='asyncNoWait'/>
works great...
What does the exe do to the xml file? WiX has custom actions which support modifying xml files during setup. They support rollback and install nothing to the target machine.
Derek
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Shmarya Rubenstein
Sent: Tuesday, August 01, 2006 2:21 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ExeCommand custom action
Hi all,
I've got an ExeCommand custom action (like this):
<CustomAction Id="LaunchConfig" FileKey="$(var.projectname).exe" ExeCommand=""[INSTALLDIR]$(var.projectname ).xml"" Return="asyncNoWait"/>
How can I make it execute with a specific working directory?
Thanks,
--
Shmarya
-----------------------------------------------------------
[EMAIL PROTECTED] - http://shmarya.net
NUnit rocks! http://nunit.com
--
Shmarya
-----------------------------------------------------------
[EMAIL PROTECTED] - http://shmarya.net
NUnit rocks! http://nunit.com
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users