Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry? And THANKS!
For DLL (and EXE) custom actions, the bitness is determined by the action's binary itself, not any marking in the MSI. In the case of DTF, the initial bitness employed will be the bitness of the sfxca.dll packaged by the wrapping action of the DTF build process. I haven't looked at the source code of sfxca.dll yet to see what inspection it makes (if any) in determining what bitness of the wrapper exe to use for the managed portion of the CA. I assume that the bitness of the sfxca.dll is determined by the Platform property of the project building and wrapping the custom action, but I haven't verified that yet either. I'll look these two things up later today unless someone else beats me to the punch and supplies the answers first. -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Sunday, October 25, 2009 12:15 AM 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? And THANKS! Good to know for future reference as I have take Blair's good advice and no longer fool with CA's to touch the registry or the event source and do those with wix elements. My only custom action left decodes a des256 string to get credentials for when I create the service and that works well. Install feels much cleaner now with the HKCU registry, and CA's for event sources and the registry stuff gone and I can live with having the user's digital detritus left behind if someone uninstalls my app ;-) There was this one caveat on the win64 attribute --> "Specifies that a script custom action targets a 64-bit platform. Valid only when used with the Script, VBScriptCall, and JScriptCall attributes" Do you think it should work with a .NET assembly which has so far been pretty easy to create and use. I'll try this sometime in the near future and report on it. Rob, Thanks for yours Blair's and everyone's help. You folks are very generous with your time and knowledge for WIX! My installs/uninstalls are running well now and so it is time to get back to getting my application and 2 services enhanced having taken time to convert from the VS2008 setup projects to WIX which I am much happier with. Switching to WIX was worth is alone just to get rid of the irritating weirdness in VS2008 where my 3 setup projects kept expanding randomly in the solution folder as I opened up other projects. And there is a lot more control in WIX and it's extendable. Thanks to all! I don't see much need for a VS2008 GUI wrapper around wix projects but would love to see some more official VS2009 integration with Powershell and WIX building or other tasks such as zipping up related files when wanting a package for someone. For a full release build, I build three x64 and three x86 msi files from a Powershell script I launch from a VS2008 project that I modified from a C# project shell. Then I have another VS2008 project zip those up with some other things such as .doc and .bat files to get my user going. It works pretty well since I can have dependencies on the other projects and with PS V2 I can catch/throw and have VS2008 stop building upon problems. - Dave -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Sunday, October 25, 2009 2:11 AM 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? If you mark your custom action as a 64-bit action it should run in a 64-bit process. I haven't tried it with DTF since I write all my custom actions in C/C++. On Sat, Oct 24, 2009 at 7:37 PM, Dave Kolb wrote: > 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 > >
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry? And THANKS!
Good to know for future reference as I have take Blair's good advice and no longer fool with CA's to touch the registry or the event source and do those with wix elements. My only custom action left decodes a des256 string to get credentials for when I create the service and that works well. Install feels much cleaner now with the HKCU registry, and CA's for event sources and the registry stuff gone and I can live with having the user's digital detritus left behind if someone uninstalls my app ;-) There was this one caveat on the win64 attribute --> "Specifies that a script custom action targets a 64-bit platform. Valid only when used with the Script, VBScriptCall, and JScriptCall attributes" Do you think it should work with a .NET assembly which has so far been pretty easy to create and use. I'll try this sometime in the near future and report on it. Rob, Thanks for yours Blair's and everyone's help. You folks are very generous with your time and knowledge for WIX! My installs/uninstalls are running well now and so it is time to get back to getting my application and 2 services enhanced having taken time to convert from the VS2008 setup projects to WIX which I am much happier with. Switching to WIX was worth is alone just to get rid of the irritating weirdness in VS2008 where my 3 setup projects kept expanding randomly in the solution folder as I opened up other projects. And there is a lot more control in WIX and it's extendable. Thanks to all! I don't see much need for a VS2008 GUI wrapper around wix projects but would love to see some more official VS2009 integration with Powershell and WIX building or other tasks such as zipping up related files when wanting a package for someone. For a full release build, I build three x64 and three x86 msi files from a Powershell script I launch from a VS2008 project that I modified from a C# project shell. Then I have another VS2008 project zip those up with some other things such as .doc and .bat files to get my user going. It works pretty well since I can have dependencies on the other projects and with PS V2 I can catch/throw and have VS2008 stop building upon problems. - Dave -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Sunday, October 25, 2009 2:11 AM 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? If you mark your custom action as a 64-bit action it should run in a 64-bit process. I haven't tried it with DTF since I write all my custom actions in C/C++. On Sat, Oct 24, 2009 at 7:37 PM, Dave Kolb wrote: > 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 it
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
If you mark your custom action as a 64-bit action it should run in a 64-bit process. I haven't tried it with DTF since I write all my custom actions in C/C++. On Sat, Oct 24, 2009 at 7:37 PM, Dave Kolb wrote: > 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 > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- 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
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
Thanks John! -Original Message- From: John H. Bergman (XPedient Technologies) [mailto:john.berg...@xpedienttechnologies.com] Sent: Saturday, October 24, 2009 11:39 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? We do this and it works for us (Same situation). Add a reference to the util extension, and add it to your namespace definitions http://schemas.microsoft.com/wix/2006/wi"; xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension"; xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";> then in the appropriate component -- 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
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
We do this and it works for us (Same situation). Add a reference to the util extension, and add it to your namespace definitions http://schemas.microsoft.com/wix/2006/wi"; xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension"; xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";> then in the appropriate component -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Saturday, October 24, 2009 5:30 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? I need a custom action to create the event source as otherwise when my 2 services and app try to write to the event log they fail. If the services/app tries to create the event source, if it does not exist, there is a supposed delay and the event log cannot be written to and this indeed seems to be the case when I have debugged this. I'm fine with installing app per machine and the only reason I want to do anything with HKCU is to make sure I clear out registry entries per user when the product is uninstalled. Maybe my app is NEVER supposed to write to HKCU if installed for all users. Is that true? Ideally I want to install/uninstall for all users but allow each actual user to have their own window coordinates and other persisted user only data. Not sure if this is allowed for. Question: If an application is installed per user for 3 users for a total of 3 installs, is there some sort of reference count kept for the # of users that installed the app such that the app is really uninstalled after the last user uninstalls it? I know Win7 and Server 2008 are different so let's not consider those in regards to this question as they seem to actually install in a user program files folder rather than the common folder. Thanks for all your help Blair! - Dave -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Saturday, October 24, 2009 5:23 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? Why do you need a custom action for event logs? Also, writing/deleting per-user content via installation packages rarely works out as well as people hope because you can't modify all the user profiles. Only the current user. In general, HKCU stuff should be managed by the application. Finally, a verbose log file should explain why a Component is not being installed. The behavior you are describing so far is not expected. There is something else. On Sat, Oct 24, 2009 at 1:33 AM, Dave Kolb wrote: > Well I flipped the order of the components in the directory node and the > feature node and still only the HKCU key got installed. > > I think I will just have a custom action update/delete the registry for me > since I have to do that with event logs anyway. > > - Dave > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Saturday, October 24, 2009 3:50 AM > 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? > > Hi Blair, you probably meant adding KeyPath to a element. > After I did that, I got this to somewhat work but only the HKCU key gets > created and not the HKLM key. No complaints during install in the log file. > I am doing a perMachine install and it seems if anything it should do the > HKLM key and not the HKCU key. Maybe it just does the second one for some > reason? > > - Thanks, Dave > > Manufacturer="$(var.Property_Author)" InstallScope="perMachine" > InstallerVersion="$(var.Property_InstallerVersion)" > Compressed="yes" > Comments="CmdMan Manager Service"/> > > > > > > > > > > > Key="Software\[MYCOMPANYNAME]\[MYPRODUCTROOT]\CmdMan.Manager.Service" > Action="createAndRemoveOnUninstall"> > KeyPath="yes"/> > > > > > Key="Software\[MYCOMPANYNAME]\[MYPRODUCTROOT]\CmdMan.Manager.Service" > Action="createAndRemoveOnUninstall"> > KeyPath="yes"/> > > > Etc... > > Level="1"> > > > Etc... > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Saturday, October 24, 2009 1:58 AM > 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? > >
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
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
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. -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Saturday, October 24, 2009 3:30 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? I need a custom action to create the event source as otherwise when my 2 services and app try to write to the event log they fail. If the services/app tries to create the event source, if it does not exist, there is a supposed delay and the event log cannot be written to and this indeed seems to be the case when I have debugged this. I'm fine with installing app per machine and the only reason I want to do anything with HKCU is to make sure I clear out registry entries per user when the product is uninstalled. Maybe my app is NEVER supposed to write to HKCU if installed for all users. Is that true? Ideally I want to install/uninstall for all users but allow each actual user to have their own window coordinates and other persisted user only data. Not sure if this is allowed for. Question: If an application is installed per user for 3 users for a total of 3 installs, is there some sort of reference count kept for the # of users that installed the app such that the app is really uninstalled after the last user uninstalls it? I know Win7 and Server 2008 are different so let's not consider those in regards to this question as they seem to actually install in a user program files folder rather than the common folder. Thanks for all your help Blair! - Dave -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Saturday, October 24, 2009 5:23 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? Why do you need a custom action for event logs? Also, writing/deleting per-user content via installation packages rarely works out as well as people hope because you can't modify all the user profiles. Only the current user. In general, HKCU stuff should be managed by the application. Finally, a verbose log file should explain why a Component is not being installed. The behavior you are describing so far is not expected. There is something else. On Sat, Oct 24, 2009 at 1:33 AM, Dave Kolb wrote: > Well I flipped the order of the components in the directory node and the > feature node and still only the HKCU key got installed. > > I think I will just have a custom action update/delete the registry for me > since I have to do that with event logs anyway. > > - Dave > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Saturday, October 24, 2009 3:50 AM > 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? > > Hi Blair, you probably meant adding KeyPath to a element. > After I did that, I got this to somewhat work but only the HKCU key gets > created and not the HKLM key. No complaints during install in the log file. > I am doing a perMachine install and it seems if anything it should do the > HKLM key and not the HKCU key. Maybe it just does the second one for some > reason? > > - Thanks, Dave > > Manufacturer="$(var.Property_Author)" InstallScope="perMachine" > InstallerVersion="$(var.Property_InstallerVersion)" > Compressed=&
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
I need a custom action to create the event source as otherwise when my 2 services and app try to write to the event log they fail. If the services/app tries to create the event source, if it does not exist, there is a supposed delay and the event log cannot be written to and this indeed seems to be the case when I have debugged this. I'm fine with installing app per machine and the only reason I want to do anything with HKCU is to make sure I clear out registry entries per user when the product is uninstalled. Maybe my app is NEVER supposed to write to HKCU if installed for all users. Is that true? Ideally I want to install/uninstall for all users but allow each actual user to have their own window coordinates and other persisted user only data. Not sure if this is allowed for. Question: If an application is installed per user for 3 users for a total of 3 installs, is there some sort of reference count kept for the # of users that installed the app such that the app is really uninstalled after the last user uninstalls it? I know Win7 and Server 2008 are different so let's not consider those in regards to this question as they seem to actually install in a user program files folder rather than the common folder. Thanks for all your help Blair! - Dave -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Saturday, October 24, 2009 5:23 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? Why do you need a custom action for event logs? Also, writing/deleting per-user content via installation packages rarely works out as well as people hope because you can't modify all the user profiles. Only the current user. In general, HKCU stuff should be managed by the application. Finally, a verbose log file should explain why a Component is not being installed. The behavior you are describing so far is not expected. There is something else. On Sat, Oct 24, 2009 at 1:33 AM, Dave Kolb wrote: > Well I flipped the order of the components in the directory node and the > feature node and still only the HKCU key got installed. > > I think I will just have a custom action update/delete the registry for me > since I have to do that with event logs anyway. > > - Dave > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Saturday, October 24, 2009 3:50 AM > 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? > > Hi Blair, you probably meant adding KeyPath to a element. > After I did that, I got this to somewhat work but only the HKCU key gets > created and not the HKLM key. No complaints during install in the log file. > I am doing a perMachine install and it seems if anything it should do the > HKLM key and not the HKCU key. Maybe it just does the second one for some > reason? > > - Thanks, Dave > > Manufacturer="$(var.Property_Author)" InstallScope="perMachine" > InstallerVersion="$(var.Property_InstallerVersion)" > Compressed="yes" > Comments="CmdMan Manager Service"/> > > > > > > > > > > > Key="Software\[MYCOMPANYNAME]\[MYPRODUCTROOT]\CmdMan.Manager.Service" > Action="createAndRemoveOnUninstall"> > KeyPath="yes"/> > > > > > Key="Software\[MYCOMPANYNAME]\[MYPRODUCTROOT]\CmdMan.Manager.Service" > Action="createAndRemoveOnUninstall"> > KeyPath="yes"/> > > > Etc... > > Level="1"> > > > Etc... > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Saturday, October 24, 2009 1:58 AM > 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? > > > Candle doesn't like Keypath on that element: error CNDL0004: The > RegistryKey > element contains an unexpected attribute 'KeyPath'. > > > -Original Message- > From: Blair [mailto:os...@live.com] > Sent: Saturday, October 24, 2009 1:22 AM > 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? > > Try adding KeyPath="yes" to each of your two RegistryKey elements. > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Friday, October 23, 200
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
Why do you need a custom action for event logs? Also, writing/deleting per-user content via installation packages rarely works out as well as people hope because you can't modify all the user profiles. Only the current user. In general, HKCU stuff should be managed by the application. Finally, a verbose log file should explain why a Component is not being installed. The behavior you are describing so far is not expected. There is something else. On Sat, Oct 24, 2009 at 1:33 AM, Dave Kolb wrote: > Well I flipped the order of the components in the directory node and the > feature node and still only the HKCU key got installed. > > I think I will just have a custom action update/delete the registry for me > since I have to do that with event logs anyway. > > - Dave > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Saturday, October 24, 2009 3:50 AM > 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? > > Hi Blair, you probably meant adding KeyPath to a element. > After I did that, I got this to somewhat work but only the HKCU key gets > created and not the HKLM key. No complaints during install in the log file. > I am doing a perMachine install and it seems if anything it should do the > HKLM key and not the HKCU key. Maybe it just does the second one for some > reason? > > - Thanks, Dave > > Manufacturer="$(var.Property_Author)" InstallScope="perMachine" > InstallerVersion="$(var.Property_InstallerVersion)" > Compressed="yes" > Comments="CmdMan Manager Service"/> > > > > > > > > > > > Key="Software\[MYCOMPANYNAME]\[MYPRODUCTROOT]\CmdMan.Manager.Service" > Action="createAndRemoveOnUninstall"> > KeyPath="yes"/> > > > > > Key="Software\[MYCOMPANYNAME]\[MYPRODUCTROOT]\CmdMan.Manager.Service" > Action="createAndRemoveOnUninstall"> > KeyPath="yes"/> > > > Etc... > > Level="1"> > > > Etc... > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Saturday, October 24, 2009 1:58 AM > 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? > > > Candle doesn't like Keypath on that element: error CNDL0004: The > RegistryKey > element contains an unexpected attribute 'KeyPath'. > > > -Original Message- > From: Blair [mailto:os...@live.com] > Sent: Saturday, October 24, 2009 1:22 AM > 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? > > Try adding KeyPath="yes" to each of your two RegistryKey elements. > > -Original Message- > From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] > Sent: Friday, October 23, 2009 6:34 PM > To: 'General discussion for Windows Installer XML toolset.' > Subject: [WiX-users] How do I add both a HKLM and a HKCU key to the > registry? > > During install, I am trying to add both an HKLM key and an HKCU key for my > product. My wxs looks like the below. When this compiles I get the error > > > >"ICE57: Component 'C_HKCU_RegistryEntries' has both per-user > and per-machine data with a per-machine KeyPath ". > > > > I have both components in the features element and since I have these > defined are separate components I do not understand why this does not work. > Any suggestions much appreciated. > > > > Thanks, Dave > > > > > > > > > > > > > > > Key="Software\[MYCOMPANYNAME]\[MYPRODUCTROOT]\Manager" > > Action="createAndRemoveOnUninstall"> > > > > > > > > > Key="Software\[MYCOMPANYNAME]\[MYPRODUCTROOT]\Manager" > > Action="createAndRemoveOnUninstall"> > > > > > > > > > > __ Information from ESET NOD32 Antivirus, version of virus > signature > database 4537 (20091023) __ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > --
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
Well I flipped the order of the components in the directory node and the feature node and still only the HKCU key got installed. I think I will just have a custom action update/delete the registry for me since I have to do that with event logs anyway. - Dave -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Saturday, October 24, 2009 3:50 AM 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? Hi Blair, you probably meant adding KeyPath to a element. After I did that, I got this to somewhat work but only the HKCU key gets created and not the HKLM key. No complaints during install in the log file. I am doing a perMachine install and it seems if anything it should do the HKLM key and not the HKCU key. Maybe it just does the second one for some reason? - Thanks, Dave Etc... Etc... -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Saturday, October 24, 2009 1:58 AM 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? Candle doesn't like Keypath on that element: error CNDL0004: The RegistryKey element contains an unexpected attribute 'KeyPath'. -Original Message- From: Blair [mailto:os...@live.com] Sent: Saturday, October 24, 2009 1:22 AM 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? Try adding KeyPath="yes" to each of your two RegistryKey elements. -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Friday, October 23, 2009 6:34 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] How do I add both a HKLM and a HKCU key to the registry? During install, I am trying to add both an HKLM key and an HKCU key for my product. My wxs looks like the below. When this compiles I get the error "ICE57: Component 'C_HKCU_RegistryEntries' has both per-user and per-machine data with a per-machine KeyPath ". I have both components in the features element and since I have these defined are separate components I do not understand why this does not work. Any suggestions much appreciated. Thanks, Dave __ Information from ESET NOD32 Antivirus, version of virus signature database 4537 (20091023) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- 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 -- 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 -- 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
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
Hi Blair, you probably meant adding KeyPath to a element. After I did that, I got this to somewhat work but only the HKCU key gets created and not the HKLM key. No complaints during install in the log file. I am doing a perMachine install and it seems if anything it should do the HKLM key and not the HKCU key. Maybe it just does the second one for some reason? - Thanks, Dave Etc... Etc... -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Saturday, October 24, 2009 1:58 AM 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? Candle doesn't like Keypath on that element: error CNDL0004: The RegistryKey element contains an unexpected attribute 'KeyPath'. -Original Message- From: Blair [mailto:os...@live.com] Sent: Saturday, October 24, 2009 1:22 AM 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? Try adding KeyPath="yes" to each of your two RegistryKey elements. -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Friday, October 23, 2009 6:34 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] How do I add both a HKLM and a HKCU key to the registry? During install, I am trying to add both an HKLM key and an HKCU key for my product. My wxs looks like the below. When this compiles I get the error "ICE57: Component 'C_HKCU_RegistryEntries' has both per-user and per-machine data with a per-machine KeyPath ". I have both components in the features element and since I have these defined are separate components I do not understand why this does not work. Any suggestions much appreciated. Thanks, Dave __ Information from ESET NOD32 Antivirus, version of virus signature database 4537 (20091023) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- 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 -- 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 -- 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
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
Candle doesn't like Keypath on that element: error CNDL0004: The RegistryKey element contains an unexpected attribute 'KeyPath'. -Original Message- From: Blair [mailto:os...@live.com] Sent: Saturday, October 24, 2009 1:22 AM 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? Try adding KeyPath="yes" to each of your two RegistryKey elements. -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Friday, October 23, 2009 6:34 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] How do I add both a HKLM and a HKCU key to the registry? During install, I am trying to add both an HKLM key and an HKCU key for my product. My wxs looks like the below. When this compiles I get the error "ICE57: Component 'C_HKCU_RegistryEntries' has both per-user and per-machine data with a per-machine KeyPath ". I have both components in the features element and since I have these defined are separate components I do not understand why this does not work. Any suggestions much appreciated. Thanks, Dave __ Information from ESET NOD32 Antivirus, version of virus signature database 4537 (20091023) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- 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 -- 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 -- 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
Re: [WiX-users] How do I add both a HKLM and a HKCU key to the registry?
Try adding KeyPath="yes" to each of your two RegistryKey elements. -Original Message- From: Dave Kolb [mailto:d...@dotnetcodeslingers.com] Sent: Friday, October 23, 2009 6:34 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] How do I add both a HKLM and a HKCU key to the registry? During install, I am trying to add both an HKLM key and an HKCU key for my product. My wxs looks like the below. When this compiles I get the error "ICE57: Component 'C_HKCU_RegistryEntries' has both per-user and per-machine data with a per-machine KeyPath ". I have both components in the features element and since I have these defined are separate components I do not understand why this does not work. Any suggestions much appreciated. Thanks, Dave __ Information from ESET NOD32 Antivirus, version of virus signature database 4537 (20091023) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- 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 -- 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
[WiX-users] How do I add both a HKLM and a HKCU key to the registry?
During install, I am trying to add both an HKLM key and an HKCU key for my product. My wxs looks like the below. When this compiles I get the error "ICE57: Component 'C_HKCU_RegistryEntries' has both per-user and per-machine data with a per-machine KeyPath ". I have both components in the features element and since I have these defined are separate components I do not understand why this does not work. Any suggestions much appreciated. Thanks, Dave __ Information from ESET NOD32 Antivirus, version of virus signature database 4537 (20091023) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- 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
