Ok,
So I think I'm getting the gist of the design now.
Because my custom action is actually modifying the target system (installing
reports), I need to make it a 'deferred' custom action.
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.
So, you guys have written a set of utility classes, so that I divide my
custom action into 2 entrypoints:
1. the 'scheduler' (configured to execute immediately) which reads all
the database information my CA will need, and 'schedules' my CA for deferred
execution, along with a serialized version of its data.
2. The 'executor' which does the actual system modifications
Later down the road, the MSI runtime executes my deferred CA, and I again
use the Wix wcautil functions to deserialize my CA data, and get to work
doing whatever I need to do...
Am I on the right track?
Thanks
Adam Langley
Secon NZ
A1/400 Rosedale Road
Albany 0632
+64 (9)414 4071
www.seconag.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
