If you use Extended="yes" you're using SecureObjects instead of 
LockPermissions.  Hopefully the verbose log file has information about what is 
getting configured.

-----Original Message-----
From: Alan Sinclair [mailto:alan.sincl...@citrix.com]
Sent: Monday, January 05, 2009 12:37
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] LockPermissions table not being created

I'm trying to set permissions on a directory, using this code:

            <Component Id="MyDestFolder"
Guid="{3E7974B0-F14A-4F9F-8CB1-D9737F658D51}"
                       DiskId="1"  KeyPath="yes">
              <CreateFolder Directory="INSTALLDIR">
                <Permission User="NetworkService"
                            Extended="yes"
                            Delete="yes"
                            GenericAll="yes">
                </Permission>
              </CreateFolder>
            </Component>

When I added the code, light complained that SchedSecureObjects was
missing until I added wixca.wixlib in the command to light.exe.

The component MyDestFolder is getting put in the MSI file, but there's
no LockPermissions table and the permissions are not getting set during
install.
Do I need to add anything else to the code, to have the table created?

Or are permissions handled entirely by the SchedSecureObjects custom
action (in which case how do I debug it)?  SchedSecureObjects looks OK
in the MSI tables, but I can't see any parameters passed to tell what
permissions to set on which objects.

Fwiw this is for Vista, and we're using WiX 2.0.5805.0.

thanks
------------------------------------------------------------------------------
_______________________________________________
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

Reply via email to