Bundles v3.x and v4.x do not see package dependencies from each other about issues

[petm2022]

I see the same problem when using the standard bootstrapper.

[barnson]

This was a behavior change to fix bug #6535.

[barnson]

Is there an option to get the bug fix in 6535 and maintain compatibility? Think about that.

Otherwise, you can hard-code the provider key in the WiX v4 build to the product code to keep compatible with the WiX v3 default.

[petm2022]

If I add <Provides Key=”GUID MsiCommon”/> to in my Wix4 bundles (A 2.0 and B 2.0) it solves the problem.

Is it possible to get the ProductCode from the msi package MsiCommon in my bundle code?
If I use !(bind.property.ProductCode) you mention in the WiX 269 Highlights I get “Unresolved bind-time variable”.

[barnson]

Turns out there's no bind-time variable for product code from a bundle. Need a new feature for that.

[tjlakixi]

I think I am experiencing this issue. Is my understanding correct that one cannot create a Wix4/5 bundle that successfully upgrades a Wix3 bundle unless <Provides Key='{productCode}'/> is added (and kept updated with new MSI versions)?
OK - my understanding was not quite correct. It only fails if the MsiPackage version (first three fields) is the same in the v3 and v4/5 bundle.

Is there a WIP for a new bind-time variable like !(bind.productCode.{projectReference}?