Ian Elliott (Excell Data Corporation) wrote: > If I condition out the component that contains the scripts, it doesn't get > installed during major upgrade. I see in the log that ComponentRegister then > registers that component as State=-7. When you finally uninstall, the > component does not get uninstalled. So, apparently conditioning the component > on major upgrade causes it to remain upon uninstall. >
I think you want to avoid component conditions if you want the state persisted across major upgrades. I'd suggest using a versioned file as the key path; that way, as long as you use a "late" RemoveExistingProducts scheduling, the component won't be upgraded but will still be uninstalled. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
