I think that there may be different ways to approach RelatedBundle. I can
only share the approach that I have been using. For every bundle I create I
assign a "relatedBundleGuid" (which is different than the UpgradeCode for
that bundle), along with a BundleTag:
<RelatedBundle Action='Detect' Id='$(var.ThisSetup_RelatedBundleGuid)' />
Then at the later time, in the addon bundle I also designate the bundle that
the addon should target. Here I am using the UpgradeCode of those other
previously deployed "Suite" Bundles (in addition to also defining the above
RelatedBundleGuid for this new Addon bundle, in the event that I need to
target it with another related bundle).
<RelatedBundle Action='Addon' Id='$(var.SuiteBundleA_UpgradeCode)' />
<RelatedBundle Action='Addon' Id='$(var.SuiteBundleB_UpgradeCode)' />
I hear your concern that the 'addon' is built without knowledge of the other
bundles. Maybe someone else has some ideas for that issue.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/R-Extend-ProductSearch-for-working-with-Burn-exe-Package-tp7600279p7600454.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
