Neil Sleightholm wrote: > ...I would suggest that the right place to do this is in > your application on first run not in the installation.
Rob Mensching wrote: > IMHO, the best way to handle this is to put the "default" > settings in the code or, if you must, put them in HKLM. Then your > application reads from HKCU and if it doesn't find the setting there > it falls back to where the default location is. That way you only > write the settings that the user changes from the default (saves time > and space). I'll take your advice and put the routine to write create the HKCU entries and default values into my application. > This is even more important since there is no good way to clean up > all HKCU registry keys on uninstall. If a user runs my application and later it is uninstalled, the users will have to live with the orphaned registry entry. Perhaps a registry cleaner will scrub it away. Few, if any, users will notice. george_r wrote: > Chuck, try: > <Property Id="ALLUSERS">1</Property> That's what InstallScope=perMachine does and from http://www.joyofsetup.com/2008/04/01/new-wix-feature-setting-package-installation-scope/: "If you specify perMachine, you must remove any Property element that sets ALLUSERS." > and set the initial registry values to HKCU. Are you sure that the HKCU registry entry exists for any user other than the one that performed the installation? In my experience only the installing user receives the HKCU entry. -- Charles ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
