Hmm.  I was ignoring your scenario because it's not possible to write an
install condition like that.  If that functionality is added, I would
expect it to be authored as one package with one payload designated as the
layout package and the other designated as the download package.

How about the scenario where you want to install .NET 4.0 on XP and .NET
4.5 on Vista and later?  In this case, you would customize the theme by
adding two controls, one for each license.  Each control would be
conditionally shown using the same conditions as the install conditions on
the packages.  You wouldn't use the new License attributes, and delete the
built in license control in the theme.  Does that work?

On Wed, Oct 22, 2014 at 9:58 AM, Bob Arnson <b...@joyofsetup.com> wrote:

>  I'm not concerned (at the moment, anyway) about needing to show multiple
> licenses or license links. I just don't see how we'd implement the scenario
> I described under your proposal. (To be clear, I'm all in favor of ridding
> us of magic variables.)
>
> On 21-Oct-14 20:46, Sean Hall wrote:
>
> Currently WixStdBA has two special controls for displaying a license
> (EulaRichEdit and EulaHyperlink).  The default themes for WixStdBA/mbapreq
> use only one of them.  That's what I meant by saying the developer will
> need to disable the default URL link.
>
>  Currently, the license gets set automatically when pulling in a .NET
> Package from NetFxExtension.  I thought it would be a good idea to figure
> out how to keep that working without using the binder variables.
>
>  I figure that needing to show multiple licenses is rare.  Developers can
> always combine all the licenses into one file, right?  They can also
> customize the theme.
>
> On Mon, Oct 20, 2014 at 11:14 PM, Bob Arnson <b...@joyofsetup.com> wrote:
>
>>  Which is the "default URL"? First? I suppose that would work, as long as
>> @After is used correctly. (To be clear, this isn't a real world problem
>> [yet] because in this case the packages are mutually exclusive and have the
>> same license.)
>>
>> On 20-Oct-14 23:54, Sean Hall wrote:
>>
>> Ugh. Force the user to customize the UI to disable the default URL link,
>> and use the new ability to conditionally hide controls to show the right
>> license?
>>
>> On Mon, Oct 20, 2014 at 10:50 PM, Bob Arnson <b...@joyofsetup.com> wrote:
>>
>>>  On 20-Oct-14 23:34, Sean Hall wrote:
>>>
>>> Since we're talking about breaking changes in v4.0, I sent a pull
>>> request <https://github.com/wixtoolset/site/pull/35> to update the WIP
>>> <http://wixtoolset.org/development/wips/4161-allow-more-than-one-mbaprereq/>
>>>  about
>>> MBA prerequisites.  As mentioned in the WIP, the WixMbaPrereqPackageId
>>> binder variables (and its license friends) couldn't be removed in 3.x.  I
>>> updated the plan for v4.0.  Feedback?
>>>
>>> From the pull request:
>>>
>>> + * Figure out how to ensure there is at least one prereq package, at
>>> most one prereq package has a License attribute, and the type of the
>>> license attribute matches the type of WixManagedBootstrapperApplicationHost
>>> that was chosen.
>>>
>>> An important case where this won't work: Consider having two .NET
>>> packages, one the full redist and the other the Web package. The install
>>> conditions say "if the full redist is available, use it (i.e., dvd or
>>> /layout), otherwise use the Web page). Both need licenses.
>>>
>>
------------------------------------------------------------------------------
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to