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

[Rob Mensching]

One thing, those issues should track a change to Burn (not wixstdba) for the default handling of "same version upgrade".

Same version upgrades was mostly a coin flip way back when (I didn't think it made sense so tipped the coin that way) and feedback says I picked wrong.

So, Burn should change its default recommendation. BAs can still override the default behavior if they want.

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Bob Arnson via wix-devs
Sent: Tuesday, June 30, 2020 3:31 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Bob Arnson <bob at firegiant.com>
Subject: Re: [wix-devs] 3746/4808 - Configuring Bundle upgrades

By all means. But I do try to help.

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

I don't agree, but I'm also not interested in arguing about it. Especially when my way is more work.

On Wed, Jul 1, 2020 at 7:48 AM Bob Arnson <bob at firegiant.com> wrote:

> We shouldn't encourage AllowDowngrades given how poorly MSI supports it.
> (Maybe, if you want to support a related-bundle mode that does the 
> previous-bundle-uninstall first.) AllowSameVersionUpgrades should just 
> be the new way things work. I don't think there's a lot of benefit to 
> the current behavior or that people would miss it.
>
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of 
> Sean Hall via wix-devs
> Sent: Tuesday, 30 June, 2020 17:36
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Cc: Sean Hall <r.sean.hall at gmail.com>
> Subject: Re: [wix-devs] 3746/4808 - Configuring Bundle upgrades
>
> I don't have a preference for what the defaults are.
>
> What I'm interested in is allowing Bundles to declaratively specify 
> "AllowDowngrades" and "AllowSameVersionUpgrades" as yes/no. Version 
> ranges probably aren't required for this, so I'd be fine with doing it differently.
>
> On Wed, Jul 1, 2020 at 1:26 AM Rob Mensching <rob at firegiant.com> wrote:
>
> > 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.
> >