I thought the goal was to be able to compile your existing project on the
next version and everything work like before. There could be someone who
set their .NET package InstallCondition to "0 = 1", and then it would be
different.
On Fri, May 16, 2014 at 7:17 PM, Rob Mensching <r...@firegiant.com> wrote:
> If there’s no use case for always then let’s just not support it. If
> there is no use case then it’s not going to be a breaking change because no
> one will have used it (successfully).
>
>
>
> _______________________________________________________________
>
> FireGiant | Dedicated support for the WiX toolset |
> http://www.firegiant.com/
>
>
>
> *From:* Sean Hall [mailto:r.sean.h...@gmail.com]
> *Sent:* Friday, May 16, 2014 5:00 PM
> *To:* WiX toolset developer mailing list
> *Subject:* Re: [WiX-devs] WIP 4161 - Allow More Than One MBA Prerequisite
>
>
>
> I'm not seeing the use case for "always". If it's always supposed to be
> installed, just don't specify an install condition (which means it always
> gets installed).
>
>
>
> I agree that the current way the Prereq BA always installs the prereq is
> bad, it's why a bundle can't do cool things like make the Prereq BA install
> .NET 4.0 on XP and 4.5.x on Vista and later.
>
------------------------------------------------------------------------------
"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
