[wix-devs] 3746/4808 - Configuring Bundle upgrades

[Rob Mensching]

We could if the additional complexity was worth it. However, AFAICT, the lack of version ranges hasn't been a real problem.

What was called out as the problem was the "AllowSameVersionUpgrades" both in Bundles and MSIs. I think I've come around (and these issues are the result of that) to the fact that same version upgrades is better than the behavior you get without allowing same version upgrades (duplicated packages).

So the default should change for both MSI and Bundles.

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Hall via wix-devs
Sent: Sunday, June 28, 2020 5:55 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Sean Hall <r.sean.hall at gmail.com>
Subject: [wix-devs] 3746/4808 - Configuring Bundle upgrades

Looking at https://github.com/wixtoolset/issues/issues/3746 and https://github.com/wixtoolset/issues/issues/4808, Burn seems to have been designed so that all Bundles have the equivalent of <MajorUpgrade AllowDowngrades="no" AllowSameVersionUpgrades="no /> without the ability to change it. All RelatedBundles with type Upgrade work the same way.

Is there a reason we shouldn't enhance Burn to support configurable version ranges for RelatedBundles? That seems like the way to go.
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/