Bugs item #1565886, was opened at 2006-09-26 10:56 Message generated for change (Settings changed) made by pmarcu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1565886&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: extensions Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: DGutride (dgutride) >Assigned to: pmarcu (pmarcu) Summary: Setting extended ACL permissions conditionally doesn't work Initial Comment: WiX 2.0.4103 SecureObj Custom Action: If a component has a condition, contains a CreateFolder element with an extended permission element within, the permissions are not set on the folder that is created. The attached code demonstrates this problem. We are using a condition to determine which user (ASPNET or IIS_WPG) should have permissions set on this folder. If the first component is removed, the install will correctly set the permissions on the created folder. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1565886&group_id=105970 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
