Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-02-02 Thread Boyd Ludlow
Is there some way to log the value of the Burn Built-in Variables. At the moment the log just tells me that my test resolved to False and I can't tell if the value of Privileged is set to False or is undefined. I've tried testing against some of the other built-in variables and had unexpected

Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-02-02 Thread Rob Mensching
Not today but it's been asked before. On Thu, Feb 2, 2012 at 3:15 AM, Boyd Ludlow boyd.lud...@gmail.com wrote: Is there some way to log the value of the Burn Built-in Variables. At the moment the log just tells me that my test resolved to False and I can't tell if the value of Privileged is

Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-01-30 Thread Boyd Ludlow
Rob, I just assumed that it was a bug because your response to that Stack Overflow question stated that the behaviour being seen was a bug. I didn't know enough about working with Burn to know if I was doing something wrong or if it was a problem with Burn but I accepted that you would know what

Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-01-30 Thread Rob Mensching
Maybe I should be more clear. When I say something is a bug, I mean The behavior you described is not expected. That does not mean there is a bug on SourceForge tracking it. Privileged in Burn means the process was launched elevated. If you are launching Burn elevated (aka: you see the consent

Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-01-28 Thread Rob Mensching
That's not a bug. That's a Stack Overflow question. If you really are hitting a bug, please open it so we can get details and track progress on the issue. On Fri, Jan 27, 2012 at 12:04 AM, Boyd Ludlow boyd.lud...@gmail.com wrote: As per this post

Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-01-27 Thread Boyd Ludlow
As per this post http://stackoverflow.com/questions/8691061/wix-3-6-burn-bootstrapper-fails-to-elevate On Fri, Jan 27, 2012 at 4:40 AM, Bob Arnson b...@joyofsetup.com wrote: On 26-Jan-12 11:18, Boyd Ludlow wrote: I know that a bug currently exists when using burn that it errors rather than

[WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-01-26 Thread Boyd Ludlow
I know that a bug currently exists when using burn that it errors rather than asking for elevated rights. I thought that then I could add a condition to prevent setup running is the user is not an admin or if they have not selected Run as admin. My attempt follows but I never seem to be able to

Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-01-26 Thread John Cooper
to get bal:Condition to work (wix burn) I know that a bug currently exists when using burn that it errors rather than asking for elevated rights. I thought that then I could add a condition to prevent setup running is the user is not an admin or if they have not selected Run as admin. My attempt

Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-01-26 Thread Boyd Ludlow
@lists.sourceforge.net Subject: [WiX-users] Struggling to get bal:Condition to work (wix burn) I know that a bug currently exists when using burn that it errors rather than asking for elevated rights. I thought that then I could add a condition to prevent setup running is the user is not an admin

Re: [WiX-users] Struggling to get bal:Condition to work (wix burn)

2012-01-26 Thread Bob Arnson
On 26-Jan-12 11:18, Boyd Ludlow wrote: I know that a bug currently exists when using burn that it errors rather than asking for elevated rights. What bug is that? -- sig://boB http://joyofsetup.com/ -- Try before you