I've posted a bug on this issue, it is fairly easy to reproduce. If you take the example that was originally submitted on this thread and change them to extended permission elements, it will demonstrate the problem. When a component is conditioned and it contains createfolder and extended permission elements, the permissions specified are not set at all.
Thanks,
Dana
On 9/26/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
Dana Gutride wrote:
> I've encountered a similar problem, it seems the permission element
> doesn't take into account the condition of the component it's within.
> This also seems to occur both with the generic MSI way of doing this
> and the extended WiX secureobj custom actions.
I'm not sure how the LockPermissions table works in MSI -- it's not
documented which actions access that table -- but the SecureObj CA
scheduler explicitly checks component install-action state (using
WcaIsInstalling). If you have a repro, please post a bug.
--
sig://boB
http://bobs.org
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
