The real question is why the ShellExecuteEx is failing. Have we tracked that
down or captured a ProcMon log so we can do some analysis as to what the
framework upgrade could of possibly hosed up?
From: Sean Hall [mailto:r.sean.h...@gmail.com]
Sent: Monday, May 26, 2014 10:14 PM
To: WiX toolset developer mailing list
Subject: [WiX-devs] .NET 4.5.2 on Win7 RTM
I was able to figure out when the MBA Host loaded .NET 4.5.2 on Win7 RTM using
the .NET 4 hosting APIs and checking the registry. I have a proof of concept
in this branch: https://github.com/rseanhall/wix3/tree/bug4416.
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?
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 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?
------------------------------------------------------------------------------
The best possible search technologies are now affordable for all companies.
Download your FREE open source Enterprise Search Engine today!
Our experts will assist you in its installation for $59/mo, no commitment.
Test it for FREE on our Cloud platform anytime!
http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
