Blair wrote: > The idea being that since remove is the opposite of install, and the > rollback does the opposite of whatever transaction you were running, then > you write the minimal amount of custom action code to make it all work > (which is only two deferred routines in your CA dll). >
Except that "install rollback" isn't the same as "uninstall" during upgrades or patching. Exactly why I prefer to use MSI's behavior as much as possible: Saving the pre-install state so you can put it back during rollback is often tough. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
