launching Burn was already elevated) and Privileged is not true, then that
> would be a bug.
>
> On Mon, Jan 30, 2012 at 2:49 AM, Boyd Ludlow
> wrote:
>
> > Rob,
> >
> > I just assumed that it was a bug because your response to that Stack
> > Overflow questio
> 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
> wrote:
>
> > As per this post
> >
>
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 wrote:
> On 26-Jan-12 11:18, Boyd Ludlow wrote:
> > I know that a bug currently exists when using burn that it errors rather
> >
ESA
> Jack Henry & Associates, Inc.(r)
> Shawnee Mission, KS 66227
> Office: 913-341-3434 x791011
> jocoo...@jackhenry.com
> www.jackhenry.com
>
>
>
>
> -Original Message-
> From: Boyd Ludlow [mailto:boyd.lud...@gmail.com]
> Sent: Thursday, Janu
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 g
5 matches
Mail list logo
