>> Hi,
>> I'm authoring an installer package that need to register a couple of DLLs in
>> the registry (traditionally done by regsvr32). I used heat.exe to generate
>> the
>> <snip>
>> After installing the package:
>> Administrator (Full control - not inherited) (the user, not the group)
>> System (Full control - not inherited)
>> Administrators (Full control - not inherited)
>> RESTRICTED (Read - not inherited)
> Ok, I figured this one out. It's not a WiX issue, but this is how Windows
> installer does it when you install a package that is "Just for me" as opposed
> to "Everyone". I assume it is OK, it just looked very strange to me.
> By adding the ALLUSERS property and setting the value to 2 (meaning install
> and make available to everyone) it works as expected. The thing is that I had
> no UI so I completely forgot about that setting.
And some additional info in case others are wondering how this works.
ALLUSERS should be set to 1 to enforce per-machine installation. The value 2
will attempt a per-machine installation and revert to per-user if the
installing user does not have the privileges to perform per-machine
installation (except on Vista where it will fail instead of revert if the
installing user fails to provide proper credentials to the UAC).
And regarding the registry and permissions, when doing a per-user installation
the registry keys are written to HKCU\Software\Classes and the HKCR key
reflects the merged version from HKLM\Software\Classes and
HKCU\Software\Classes. That's why the permissions looked strange, but they were
of course only for _my_ user and not for everyone.
Arild
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
