Mike Dimmick wrote:
The WiX custom actions perform their install/uninstall actions on a
per-component basis by calling MsiGetComponentState. If the resource
is currently installed locally or to run from source, and the action
is to make it absent or removed, the uninstall tasks are performed.
It's probably a good idea to stick to this model.
It also makes it easier to support patching, upgrade, and repair
scenarios over all-or-nothing install/uninstall choices.
--
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-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
