Re: [WiX-users] Registry permission for key and subkeys
Ok, I opened bug 3029343 for the issue. Andreas Hirth -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Saturday, July 10, 2010 5:01 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Registry permission for key and subkeys On 7/9/2010 12:23 PM, Andreas Hirth wrote: thanks for pointing that out. Obviously with this information I could fix the behavior by patching the WiX sources and building my own binaries. But looking at the current head of the 3.5 development I see the same code there as in 3.0. So I guess it is not planned to change the behavior. Or nobody entered a bug so the WiX team doesn't know about it. -- sig://boB http://joyofsetup.com/ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registry permission for key and subkeys
Hmm... that's a point. I will see if I manage to open a bug for that. Andreas Hirth -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Saturday, July 10, 2010 5:01 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Registry permission for key and subkeys On 7/9/2010 12:23 PM, Andreas Hirth wrote: thanks for pointing that out. Obviously with this information I could fix the behavior by patching the WiX sources and building my own binaries. But looking at the current head of the 3.5 development I see the same code there as in 3.0. So I guess it is not planned to change the behavior. Or nobody entered a bug so the WiX team doesn't know about it. -- sig://boB http://joyofsetup.com/ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Registry permission for key and subkeys
Hi all, I'm struggling with the task to apply security settings to a registry key. What I want to achieve is setting full access to Everyone for a registry key, and I want this being inherited. Unfortunately I only get as far as setting the full access right for Everyone on the key, but it applies This key only: RegistryKey Root=HKLM Key=SOFTWARE\Foo Action=create util:PermissionEx User=Everyone GenericAll=yes / /RegistryKey However, I need it to apply to This key and subkeys. Is there any way to get this working other than a custom CustomAction? Any advise is much appreciated! Andreas Hirth -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registry permission for key and subkeys
That's exactly the problem. The permission must be inherited to keys created later by the application. I already have the code to put in a custom action but I try to use built-in functionality as much as possible. So I would prefer if there was a way to do it natively with Windows Installer or WiX. Andreas Hirth -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Friday, July 09, 2010 1:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Registry permission for key and subkeys My colleague had this same problem. If you have a limited number of keys that are known at install time, you can add them all explicitly and set permissions on them. Since we wanted the permissions to cascade down to keys created by the application and we were short of time, we used wix's qtexec custom action to run an open source utility called SetACL. http://setacl.sourceforge.net/ -Original Message- From: Andreas Hirth [mailto:a.hi...@luratech.com] Sent: 09 July 2010 09:47 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Registry permission for key and subkeys Hi all, I'm struggling with the task to apply security settings to a registry key. What I want to achieve is setting full access to Everyone for a registry key, and I want this being inherited. Unfortunately I only get as far as setting the full access right for Everyone on the key, but it applies This key only: RegistryKey Root=HKLM Key=SOFTWARE\Foo Action=create util:PermissionEx User=Everyone GenericAll=yes / /RegistryKey However, I need it to apply to This key and subkeys. Is there any way to get this working other than a custom CustomAction? Any advise is much appreciated! Andreas Hirth -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users /pre BR style=font-size:4px; a href = http://www.sdl.com;img src=http://www.sdl.com/images/email logo_150dpi-01.png alt=www.sdl.com border=0//a BR font face=arial size=2 a href = http://www.sdl.com; style=color:005740; font-weight: boldwww.sdl.com/a BR BR font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.BR SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.BR Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. /font -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registry permission for key and subkeys
Peter -- thanks for pointing that out. Obviously with this information I could fix the behavior by patching the WiX sources and building my own binaries. But looking at the current head of the 3.5 development I see the same code there as in 3.0. So I guess it is not planned to change the behavior. This would mean that I had to patch and rebuild with every new WiX release I want to use. I don't think that's what I want to do. So I will go with a CustomAction. Thanks again! Andreas Hirth -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Friday, July 09, 2010 3:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Registry permission for key and subkeys Sadly, you cant do it. Yan found the specific bit of code that causes this problem so if you are prepared to recompile wix yourself, you could make the fix. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registry-P ermissions-td2939332.html#a2939332 -Original Message- From: Andreas Hirth [mailto:a.hi...@luratech.com] Sent: 09 July 2010 13:24 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Registry permission for key and subkeys That's exactly the problem. The permission must be inherited to keys created later by the application. I already have the code to put in a custom action but I try to use built-in functionality as much as possible. So I would prefer if there was a way to do it natively with Windows Installer or WiX. Andreas Hirth -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Friday, July 09, 2010 1:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Registry permission for key and subkeys My colleague had this same problem. If you have a limited number of keys that are known at install time, you can add them all explicitly and set permissions on them. Since we wanted the permissions to cascade down to keys created by the application and we were short of time, we used wix's qtexec custom action to run an open source utility called SetACL. http://setacl.sourceforge.net/ -Original Message- From: Andreas Hirth [mailto:a.hi...@luratech.com] Sent: 09 July 2010 09:47 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Registry permission for key and subkeys Hi all, I'm struggling with the task to apply security settings to a registry key. What I want to achieve is setting full access to Everyone for a registry key, and I want this being inherited. Unfortunately I only get as far as setting the full access right for Everyone on the key, but it applies This key only: RegistryKey Root=HKLM Key=SOFTWARE\Foo Action=create util:PermissionEx User=Everyone GenericAll=yes / /RegistryKey However, I need it to apply to This key and subkeys. Is there any way to get this working other than a custom CustomAction? Any advise is much appreciated! Andreas Hirth -- -- -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users /pre BR style=font-size:4px; a href = http://www.sdl.com;img src=http://www.sdl.com/images/email logo_150dpi-01.png alt=www.sdl.com border=0//a BR font face=arial size=2 a href = http://www.sdl.com; style=color:005740; font-weight: boldwww.sdl.com/a BR BR font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.BR SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.BR Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. /font -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
Re: [WiX-users] how to select the previously installed features by default while upgrading
Hello, just set MigrateFeatures=yes in your UpgradeVersion element. http://wix.sourceforge.net/manual-wix3/wix_xsd_upgradeversion.htm Andreas Hirth -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Thursday, July 08, 2010 2:45 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] how to select the previously installed features by default while upgrading Hi, I have a installer which has three independent features. user can select any of them. when user upgrades to newer version, how can I select only those features which were installed with previous version ? Regards, Sanjay Rao -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditionally install executable as service
Thanks a lot for the replies. The approach with two components is working for me now. My mistake was to not define the conditions fully exclusive. Thats why I got ICE30. Setting two different ShortNames manually was not necessary. Thanks again, Andreas LuraTech Imaging GmbH Ulmenstr.22 42855 Remscheid Tel.: +49 (0)30 / 39 40 50 - 0 Fax : +49 (0)30 / 39 40 50 - 99 www.luratech.com Amtsgericht Wuppertal HRB 17025 Geschäftsführer: Dipl.-Ing. Carsten Heiermann -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Monday, May 17, 2010 8:04 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditionally install executable as service I would probably be doing two Components as you mention in your last attempt. The ICE30 error is probably related to duplicate shortnames. You can probably get around this by specifying your own shortnames rather than having WiX generate them for you. It might be giving each Component the same shortname, or trying to anyway. I'd be looking at that since I agree you can't condition a ServiceControl by itself from the look of it. -Original Message- From: Andreas Hirth [mailto:a.hi...@luratech.com] Sent: Monday, May 17, 2010 8:59 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditionally install executable as service Hi all, I struggle with writing a WiX installer that can conditionally install an executable as Windows service. The executable can be run as Windows service but it is not required to. The user should get an option to install the service during setup or not. The option could be in form of a feature Install as Windows Service. I'm stuck because the ServiceInstall element has no condition and always refers to the KeyPath file of its Component. My last attempt was to have two Components installing the same file, one with ServiceInstall, the other without. But besides not being a very elegant approach it's not working (ICE30). Is there any solution out there you know of or would the only way to write my own custom action for this? Any help would be appreciated. Thanks! Andreas -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditionally install executable as service
Hi all, I struggle with writing a WiX installer that can conditionally install an executable as Windows service. The executable can be run as Windows service but it is not required to. The user should get an option to install the service during setup or not. The option could be in form of a feature Install as Windows Service. I'm stuck because the ServiceInstall element has no condition and always refers to the KeyPath file of its Component. My last attempt was to have two Components installing the same file, one with ServiceInstall, the other without. But besides not being a very elegant approach it's not working (ICE30). Is there any solution out there you know of or would the only way to write my own custom action for this? Any help would be appreciated. Thanks! Andreas -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
