Re: [WiX-users] Conditional Folder Permission

2006-09-27 Thread Mike Dimmick
wouldn't expect to see this in WiX 2.0, though.   -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dana GutrideSent: 26 September 2006 18:59To: wix-users@lists.sourceforge.netSubject: Re: [WiX-users] Conditional Folder Permission Bob:I've posted a bug on

Re: [WiX-users] Conditional Folder Permission

2006-09-26 Thread Dana Gutride
Bob: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 per

Re: [WiX-users] Conditional Folder Permission

2006-09-26 Thread Mike Dimmick
: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Conditional Folder Permission 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

Re: [WiX-users] Conditional Folder Permission

2006-09-26 Thread Bob Arnson
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

[WiX-users] Conditional Folder Permission

2006-09-26 Thread gcoates
Hi All, The info on this forum is very useful. Thanks. I have an issue, our application needs a different set of permissions set on a directory depending on the windows os. Ive coded this below, I want the first permission to be set if we are installing on WinXP or W2003 and the second set to be

Re: [WiX-users] Conditional Folder Permission

2006-09-26 Thread Dana Gutride
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. DanaOn 9/26/06, gcoates <[EMAIL PROTECTED]>