Thanks for responding. The main problem I see with your modifications is
backwards compatibility.
Believe it or not, the Prereq BA *always* installed the prereq package, it
didn't pay attention to its InstallCondition.
As a binder variable, you will still be forced to specify the
MbaPrereqPackageId and the url.
It doesn't really make sense to call it a support package if the goal is to
make all of the packages equal.
On Fri, May 16, 2014 at 6:24 PM, Rob Mensching <r...@firegiant.com> wrote:
> I’ve bulked up the WIP a bit with my pull request at:
> https://github.com/wixtoolset/site/pull/16
>
>
>
> Sean, I’m curious if that aligns with how you were seeing the feature
> implemented.
>
>
>
> If so, I think that is the way to go. The original design was done for
> expediency (you would be surprised how close we were to having no managed
> code BA solution for a while).
>
>
>
> I do think something like WIP #4161 (
> http://wixtoolset.org/development/wips/4161-allow-more-than-one-mbaprereq/and
> https://github.com/wixtoolset/site/pull/16) is ideal.
>
>
>
> _______________________________________________________________
>
> FireGiant | Dedicated support for the WiX toolset |
> http://www.firegiant.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
