responses inline:
> From: d...@vulscan.com
> Date: Wed, 17 Jul 2013 08:15:51 -0700
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Understanding WiX elevation and BHO
>
> Hey Blair,
>
> Thank you for the input. Great insights here.
>
> I al
On Wed, Jul 17, 2013 at 8:15 AM, Dana Epp wrote:
> Execute
> ="deferred"
> ExeCommand='/install="[INSTALLFOLDER]$(var.Our.App.TargetFileName)"
> /privileges=admin /returnExitCode=false' Impersonate="yes" />
>
One reason why this CustomAction works from an elevated command prompt but
not from a
gt;
> Blair Murri
>
> > From: d...@vulscan.com
> > Date: Tue, 16 Jul 2013 20:53:47 -0700
> > To: wix-users@lists.sourceforge.net
> > Subject: [WiX-users] Understanding WiX elevation and BHO
> >
> > Hey guys,
> >
> > I am still rather new to WiX an
ue diligence one would give to learning any
new language/environment, etc.
Blair Murri
> From: d...@vulscan.com
> Date: Tue, 16 Jul 2013 20:53:47 -0700
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Understanding WiX elevation and BHO
>
> Hey guys,
>
>
Hey guys,
I am still rather new to WiX and I am confused on some behavior relating to
the generated MSI.
It surrounds the registration of a browser helper object (BHO) for Internet
Explorer. The current test bed is on Windows 8 Enterprise, but it should
have the same affect on earlier versions of
5 matches
Mail list logo