Adam Langley wrote:
The code in WiX appears only to read from the MSI tables when
/installing/, but relies on serialized data from the Metabase upon
rollback/uninstall, is that correct (Im making a big assumption around
what on earth the 'MetaBase' is, and what's its for)?
Generally, the scheduling CAs run every time, read the custom table
which includes a component reference, and use the state of the component
to determine what to do. For example, if the install state of the
component is 'absent' and the action state is 'install local,' then the
scheduling CA needs to write custom action data to install the widget.
Likewise, 'installed local' to 'absent' means remove the widget and so
on. That makes it fairly easy to support patching and repair too because
you can make the right decision in the same code path. It also means
that CAs don't have to persist much data between installations.
--
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
