[wix-devs] Bundles: RelatedBundle Upgrade and Min/Max version

[Hoover, Jacob]

I guess to be fair it would be more like...
1.5.2 = Good
1.6.0->1.6.9 -= Bad (Used 1.5 Upgrade codes)
1.6.10 = Fixing

And we wish to support 1.5 and 1.6 installed at the same time. 

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Hoover, Jacob
Sent: Monday, August 14, 2017 11:04 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] Bundles: RelatedBundle Upgrade and Min/Max version

Yeah, normally I do but in this case I had missed in QA that the upgrade code didn't change.  So now I have an install that looks like:

1.5.2 = Good Old Bundle we want to keep/allow to install.
1.5.3 -> 1.5.9 = Tainted bundles, it upgraded the MSI's (MSI upgrade codes also didn't change) and put the installation in a new installroot but didn't update the upgrade code.
1.5.10: "Future Fixed bundle"

I would change the upgrade codes in both the MSI's and the bundles, but I want 1.5.10+ to remove 1.5.3->1.5.9, yet allow a user to still install 1.5.2 (or allow them to keep 1.5.2 if they hadn't taken the tainted updates).

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Rob Mensching
Sent: Monday, August 14, 2017 10:58 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] Bundles: RelatedBundle Upgrade and Min/Max version

Did you consider changing the UpgradeCode?

Regards,

  Rob Mensching
  CEO
  FireGiant
_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Hoover, Jacob
Sent: Thursday, August 10, 2017 10:33 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: [wix-devs] Bundles: RelatedBundle Upgrade and Min/Max version

Correct me if I am wrong, but we don't currently support a Upgrade table for related bundles similar to the Msi Upgrade table. As such, if one wanted to target specific versions of related bundles, they would need to write their own  BA. Do you think this would be a feature that WixStdBA should support?

Ex:
<RelatedBundle Id="{GUID}" Action="Upgrade" MinVersion="1.5.3" MaxVersion="1.5.9" />

I know no new features for 3.x, so then an interesting option comes into play.  Assuming Sean's messaging approach was extended for BAF's for all callbacks, that means one could write a BAF for the DetectRelatedBundle callback, and put any custom logic needed in there.

Which would be the preferred approach?

Thanks,
Jacob

____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/ ____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/ ____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/