Neil Sleightholm wrote: > When I approached this it seemed a really simple requirement - all I want was > "set registry key to 1 if feature selected, set to 0 if not". It works ok on > initial install but seem impossible on "Change". >
As long as you're just ADDLOCALing and REMOVEing features, no component will get reinstalled. So try this: 1. Move the component tied to the registry resource into its own feature. 2. In InstallExecuteSequence, before CostInitialize, set REINSTALL to that feature when doing a Change. You'll have to play around with #2 a bit; I'm just extrapolating from the doc on the timing needed and you'll have to get the condition right. The idea is to let the user pick features to add and remove but to reinstall the registry feature only when not initially installing or repairing, uninstalling, or major-upgrading the whole product. Then REINSTALLMODE kicks in and you can get the overwrite behavior you're looking for. -- 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
