Thank you for your help! We eventually figured it out, here is a snippet of
our working source
<Binary
Id="ExecuteCommand"
SourceFile="path\to\exe\ExecuteCommand.exe" />
<CustomAction
Id="checkDependencies"
BinaryKey="ExecuteCommand"
Impersonate="yes"
Execute="deferred"
ExeCommand="perl 'checkDependencies.pl'"
Return="check" />
We had to write our own exe to do it however, but that was not really a
problem.
Now we are trying to figure out how we can get the perl scripts into the
msi, unpacked and on the new system, and run them before install. Is there a
way to include the .pl files and our ExecuteCommand.exe in the msi like you
would normal components and write them before the other files, or to include
them a separate way and have them still be written to disk before the actual
install occurs.
Thanks again,
Dan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Perl-Script-on-initialization-tp7578584p7578865.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
