[wix-users] Disallowing Old Bundle/MsiProduct from Installing when they have different UpgradeCodes

[Edwin Castro]

I'll give RelatedBundle a try. Thanks!

There are already MSIs out in the field with different UpgradeCodes so I'm
stuck there. We only release the bundle so we may be okay there. *fingers
crossed*

--
Edwin G. Castro

On Fri, May 25, 2018 at 9:35 AM, Hoover, Jacob <Jacob.Hoover at greenheck.com>
wrote:

> RelatedBundle, assuming your using a recent version of WiX.
>
> When you make BundleC, add a RelatedBundle referencing A, then A's
> detection logic will see C as a newer version.
>
> If your allowing the MSI to be installed without your bundle, you would
> need to use the same UpgradeCode to allow the old MSI to see that a newer
> version is installed.
>
> https://msdn.microsoft.com/en-us/library/windows/desktop/
> aa370840%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
>
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf
> Of Edwin Castro via wix-users
> Sent: Thursday, May 24, 2018 5:38 PM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Cc: Edwin Castro <egcastr at gmail.com>
> Subject: [wix-users] Disallowing Old Bundle/MsiProduct from Installing
> when they have different UpgradeCodes
>
> Suppose I start with a BundleA with upgrade code A which installs
> MsiProductB with upgrade code B. Later we retired BundleA/MsiProductB and
> replace it with BundleC with upgrade code C which installs MsiProductD with
> upgrade code D. The versions for BundleC and MsiProductD are always higher
> than BundleA and MsiProductB. BundleC and MsiProductD are authored so that
> they automatically upgrade BundleA and MsiProductB.
>
> Suppose that a customer installs BundleC/MsiProductD on a system and then,
> later, erroneously attempts to install BundleA/MsiProductB. Since
> BundleA/MsiProductB do not know about BundleC/MsiProductD at all they
> contain no searches or launch conditions to avoid installing them when the
> newer BundleC/MsiProductD are already installed.
>
> Of course, I could create new versions of BundleA/MsiProductB that do know
> about BundleC/MsiProductD and contain the appropriate searches and launch
> conditions but that doesn't help me with old versions that don't know about
> them!
>
> Has anybody ran into something similar? If so, how did you try to avoid
> the old stuff installing and breaking the newer stuff?
>
> --
> Edwin G. Castro
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>