For the licensing issue, the Prereq BA UI is customizable just like
WixStdBA. You can add as many RichEdit controls as you wish, which means
as many licenses as you want. This shouldn't be a factor regarding
supporting "N" packages.
There are a couple of problems with the original design of the
WixMbaPrereqPackageId variable. It's a magic variable, which has already
been designated as a bad idea. It assumes that an MBA only needs one
package to get up and running, which was a bad assumption even before Burn
was released since this issue's parent issue was submitted before Burn was
released. I *really* don't like the idea of only supporting X packages.
As I pointed out, 1 .NET package + 1 support package isn't good enough.
Which means it sounds like you're asking for MbaPrereqSupport1PackageId,
MbaPrereqSupport2PackageId, MbaPrereqSupport3PackageId, ... elements on the
ManagedBootstrapperHost element, which I don't like either.
This feature's parent was opened before Burn was released. The main use
case is XP, which means it'll probably be even harder to get this into 4.0.
Please help me get this designed in time to get into 3.9 (since it sounds
like this is the last opportunity to get it into 3.x).
On Tue, May 13, 2014 at 7:24 PM, Sean Hall <r.sean.h...@gmail.com> wrote:
> Right now there is a difference in behavior. The MbaPrereqPackageId is
> used for preventing infinite loops in launching the prereq BA, I didn't
> touch that logic.
>
> Let's be honest, this is a feature for XP. Although I could see the same
> thing happening to Windows 7 and .NET 5 in a few years.
>
>
> On Mon, May 12, 2014 at 10:19 PM, Bob Arnson <b...@joyofsetup.com> wrote:
>
>> On 12-May-14 11:40, Sean Hall wrote:
>>
>> 1. WixMbaPrereqPackageId is just used during compilation. The Prereq
>> BA gets the MbaPrereqPackageId from BootstrapperApplicationData.xml, just
>> like where I put the new information.
>>
>>
>> Right. My point is that both end up with the same behavior, so they
>> should be authored the same. ("There should be one-- and preferably only
>> one --obvious way to do it."
>> <http://legacy.python.org/dev/peps/pep-0020/><http://legacy.python.org/dev/peps/pep-0020/>)
>>
>>
>> 2. A use case that needs two supporting packages is using the await
>> keyword in .NET 4.0 on XP. You'll need the WIC prereq from the original
>> bug, and the MSU package KB2468871.
>>
>>
>> XP again. :)
>>
>> --
>> sig://boBhttp://joyofsetup.com/
>>
>>
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> Get unparalleled scalability from the best Selenium testing platform
>> available
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> WiX-devs mailing list
>> WiX-devs@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-devs
>>
>>
>
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
