On Thu, May 29, 2014 at 11:50 AM, Bob Arnson <b...@joyofsetup.com> wrote:
> On 26-May-14 23:14, Sean Hall wrote:
> > The question is: what should the MBA Host do? Show a simple message
> > box, add a new page to the MBA prereq BA, fail silently, something else?
> It's comparable to Bundle/@Condition: Show a system error message. Log
> the details, of course. A more detailed error in PreqBA would be a bonus.
>
I'll make the PreqBA go straight to the Failure page. How does this sound:
"[WixBundleName] cannot run on Windows 7 RTM with .NET 4.5.2 (or greater)
installed."
>
> > Apparently everything works fine if the bundle is run elevated, or
> > Win7 is 32-bit. Should the MBA Host just let the bundle run in those
> > situations?
> I vote no. At least unless we root-caused the CLR bug. :)
>
Ok, I didn't have a preference. As far as root-causing the CLR bug, that's
out of my expertise. I tried creating a separate thread just for running
ShellExecuteEx just in case there was something wrong with the COM context,
but that didn't change anything.
>
> > I have a feeling that if the elevation was done by the application
> > manifest instead of the 'runas' verb, it would work fine. Maybe the
> > long term solution is to somehow move the elevation from
> > ShellExecuteEx to the manifest?
> That means the BA runs elevated, which is ten kinds of bad.
>
That's where the "somehow" comes in. Like maybe creating another stub .exe
that has in its manifest "requireAdministrator" and embedding that in the
setup.exe.
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
