I would give the two bundles a different Bundle/@UpgradeCode (using <?if ...?> and $(var.UpgradeCode) ), and then add a Util:ProductSearch for the other UpgradeCode. (Or rather than the Util:ProductSearch implement the detect the other bundle in the BA with BAFunctions.dll, or in an mba.) If you want to keep the same Upgradecode then write a unique registry entry and check for it in the other bundle. I have not done this sort of thing so maybe I am not aware of some constraint.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-bundle-with-prerequisite-download-and-one-with-prerequisite-compressed-but-be-equivalent-bundles-tp7594180p7594183.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
