All of the MSMQ and COM+ stuff was contributed by Frederik Grohn. So, I'd say
there is a very good chance of taking another CustomAction on.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Langley
Sent: Wednesday, June 27, 2007 10:53 PM
To: [email protected]
Subject: Re: [WiX-devs] scheduling deferred custom actions for SSRS publication
Great, thanks Bob.
Its definitely getting lots more complicated the deeper I delve, but the code
is well written so its not too difficult to understand (this is my first
significant foray into c++ for many years, I've been reserved to the Java/C#
camps since last decade).
Im currently taking my code and attempting to reformat it (and rename files)
and split everything up much like the SQL CA, in the hope that will teach me
whats going on.
If I get it all working, and it looks very much like it was written by one of
you guys (Im kinda using scasql*.* as 'templates'), would it be easy enough to
integrate into your source tree so that I can have it available in MS built
releases of Wix in the future? That would be ideal for me...
Cheers Bob
- Adam Langley
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, 28 June 2007 5:22 p.m.
To: Adam Langley
Cc: [email protected]
Subject: Re: [WiX-devs] scheduling deferred custom actions for SSRS publication
Adam Langley wrote:
Because my custom action is actually modifying the target system (installing
reports), I need to make it a 'deferred' custom action.
Right.
That means that it won't necessarily execute within the confines of the MSI,
hence the custom action may not be able to get a reference to the database to
read the information it needs.
To really explain it I need a whiteboard.<g> Basically, the execute sequence is
broken up into phases. The first is script-generation, when immediate custom
actions run and determine the actions -- and their data. Then the script is
run; that's when you have very limited access to the database and the installer
session it's running in. It's also when CAs get elevated, so they can modify
per-machine data.
There's also rollback, when MSI unwinds the script and deletes files, puts back
overwritten ones, etc. That's why deferred CAs need "matching" rollback CAs, to
undo what they did.
And there's commit, but let's not go there.<g>
Am I on the right track?
Exactly!
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
