dB. wrote:
That doesn't work. A component's condition applies to installation. So
once a component is installed, you can't conditionally uninstall it
when you remove the entire application, which happens during the major
upgrade.
Yeah, sorry, I wasn't keeping that in mind. That said, the different
scheduling options for RemoveExistingProducts would produce different
results. After InstallFinalize, for example, the component wouldn't
necessarily be uninstalled.
As Markus Kuehni wrote in his previous post, MSI keeps doing the
"right thing", which is to keep track of files and never leave
anything behind. I think an extended file copy/move/delete would be a
nice and simple WIX extension invoking the custom action and one could
specify a condition on that.
I have a rough design for a table-driven custom action that would
persist files and/or registry data to a temporary file from the upgraded
package then restore it during the installation of the upgrade package.
But I haven't needed it, so it's fallen lower on my priority list.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
