That's the way I meant it; it's dark's fault. The exception messages
aren't very user friendly. I was just trying not to spark a holy war
because all tools have their advantages and disadvantages.
________________________________
From: Christopher Painter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 09, 2007 10:22 AM
To: Paul McCloskey; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Running an executable in the binary table
No problem.
You may not have meant it the way you wrote it... but I don't agree with
the concept of InstallShield making dark throw exceptions. That is
all dark's doing.
Paul McCloskey <[EMAIL PROTECTED]> wrote:
Thanks for the help and example snippet Chris, the explanation
makes perfect sense and works like a charm. I tried going the dark
route, but our IS generated MSI files make dark throw exceptions.
Paul
________________________________
From: Christopher Painter [mailto:[EMAIL PROTECTED]
Sent: Monday, October 08, 2007 10:00 PM
To: Paul McCloskey; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Running an executable in the binary
table
A type 3074 is just a Type 2 EXE CA stored in the binary table
with the msidbCustomActionTypeInScript +
msidbCustomActionTypeNoImpersonate attributes set. This means it's a
deferred CA that runs as System Context and must be sequenced between
InstallInitialize and InstallFinalize.
You could dark an InstallShield built MSI to get some XML to
look at or you could dig through sparse schema documentation or you
could use a tool like WiXAware to help you out. That's what I did (
I'm sorry... I'm a pretty smart guy but life is too short to be writing
installs using a text editor IMO ). A sample CA snippet would look
like:
<Binary Id="Notepad.exe" SourceFile="C:\windows\notepad.exe">
</Binary>
<CustomAction Id="CustomAction1" Return="check" HideTarget="no"
Execute="deferred" Impersonate="no" TerminalServerAware="no"
ExeCommand="" BinaryKey="Notepad.exe">
</CustomAction>
<InstallExecuteSequence>
<Custom Action="CustomAction1" After="InstallInitialize" />
</InstallExecuteSequence>
Paul McCloskey <[EMAIL PROTECTED]> wrote:
Hello,
I'm trying to convert an existing Installshield project
to Wix 3.0. I'm having trouble getting my head around recreating a
custom action. The IS project runs an executable in the binary table as
a type 3074 custom action, is there an equivalent in WIX?
Thanks.
------------------------------------------------------------------------
-
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
________________________________
Tonight's top picks. What will you watch tonight? Preview the
hottest shows
<http://us.rd.yahoo.com/tv/mail/tagline/tonightspicks/evt=48220/*http:/t
v.yahoo.com/%20%0d%0a> on Yahoo! TV.
________________________________
Looking for a deal? Find great prices on flights and hotels
<http://us.rd.yahoo.com/evt=47094/*http:/farechase.yahoo.com/;_ylc=X3oDM
TFicDJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20->
with Yahoo! FareChase.
-------------------------------------------------------------------------
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
