Good information Blair and thanks. I did not know about the EventSource element but should have guesses there likely was one.
I will rethink what I am doing with the registry given your guidelines. Especially since I just realized that my custom action, built for "Any CPU", is running against the 32 bit hive and I have to drop into Win32 Interop if I want to set registry redirection which I could but would rather not do. Not that I will necessarily pursue this same path, but for future reference, is there a way to force DTF to run a managed custom action written for "Any CPU" to run in 64 bit mode besides compiling the assembly for "x64"? - Dave -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Saturday, October 24, 2009 7:09 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry? Back in the good-old-days we simply wrote in the registry until it looked like what this page describes: http://msdn.microsoft.com/en-us/library/aa363661(VS.85).aspx However, the Wix Util Extension does have an EventSource element that seems to fit the billing. Does it not work for you? If you install per-user for three different users, each installation is independent from the others. Per-user installations should never install anything "common" unless they have some independent means of coordinating the use of the common areas. That is why the WiX implementation of the per-user/per-machine switch creates a program installation directory inside of the user profile. Per-user data (such as windows coordinates, etc.) are considered user data, not program data, and are typically left behind. Besides, if your per-machine program is used by three users, there is no safe way to "clean" that data from any of the users not running the installation. Today's best practice says: the installation of per-machine programs supply "default" configuration in HKLM and never touch HKCU. The program itself manages HKCU for each user's customizations to that configuration, and that is then considered "user data". You then migrate it during first launch of your application after you upgrade, and you orphan it when you uninstall. That way there is ZERO user-profile anything in your MSI. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
