Skip to content

Bundles v3.x and v4.x do not see package dependencies from each other #7778

@petm2022

Description

@petm2022

Bugs

  • Which version of WiX are you building with?

v3.11 and v4.01

  • Which version of Visual Studio are you building with (if any)?

Visual Studio 2022 17.6.4

  • If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?

Windows 10

I have these four Managed Bootstrapper applications (bundles):

  1. Bundle A 1.0 (WiX3)
  2. Bundle A 2.0 (WiX4)
  3. Bundle B 1.0 (WiX3)
  4. Bundle B 2.0 (WiX4)
    All four bundles install several different msi packages, but they also have one msi package (MsiCommon) in common.

Scenario 1: (as expected)
• Install Bundle A 1.0 and B 1.0 (or Bundle A 2.0 and B 2.0)
• Uninstall one of them and MsiCommon is still present due to dependency, see log:
Will not uninstall package: MsiCommon, found dependents:
Found dependent: {guid}, name: My MsiCommon

Scenario 2:
• Install Bundle A 1.0 (WiX3)
• Upgrade with A 2.0 (WiX4)
• The MsiCommon package is uninstalled by the cleanup of Bundle A 1.0

Scenario 3:
• Install Bundle A 1.0 (WiX3)
• Install Bundle B 2.0 (WiX4)
• Uninstall either A 1.0 or B 2.0 and the MsiCommon will be uninstalled (no dependencies found)

Conclusion:
It looks like bundles build with WiX3 cannot see dependencies from bundles build with WiX4 and vice versa.
In registry I can see that WiX4 dependencies have a version on the GUID but WiX3 have not:

{GUID MsiCommon}
---Dependents
------{GUID Bundle A 1.0}
{GUID MsiCommon}_v1.0.0
---Dependents
------{GUID Bundle B 2.0}

Metadata

Metadata

Assignees

No one assigned

    Labels

    burnup for grabsNo one volunteered to fix the issue. If you are interested, comment with "I want to fix this issue"

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions