I seem to have hit a bug with quotes in CustomAction. Note the variations
below.
<CustomAction Id='MyCustomAction' FileKey='someExe'
ExeCommand='"[MYDIR1]" "[MYDIR2]"' Return='asyncNoWait' />
<CustomAction Id='MyCustomAction' FileKey='someExe'
ExeCommand='"[MYDIR1]" "[MYDIR2]"' Return='asyncNoWait'
/>
Either of these should work. However, when the command line parameters are
expanded out the [MYDIR2] path winds up with no quote in front of it, which
presumably causes the call to the executable to fail. I am seeing this via
the logging system of the executable. I suppose there's a chance that it's
not telling me the right thing, but that's the only logging I have to go on
because when I run the MSI with verbose logging it inextricably does not
show me what's being called or the command line parameters. You'd think that
was a pretty basic thing to log. So, after two days on this I am left blind,
and blocked from making progress. Perhaps I'll give up and fork out the
$2000 for InstallShield. Yuck.
Any tips on how to get along more nicely with Wix are most appreciated.
Thanks
Kevin
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
