Yes. It is just defined so that someday in the future I could, if needed, deploy a patch, addon, or upgrade. But at this point A - D are all MajorUpdate of A (and I did not redefine the ReleatedBundl_GUID between then. Should I change that with each MajorUpgrade? (I have been dong this for most of the last year with 3.7 and 3.8 and never encountered this behavior, which would have been noted. It is pretty obvious when observed.)
I wonder if this behavior, which I did not observe with 3.8.1128, is related to the following discussion. I am still trying to understand the discussion and research it. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Is-adding-a-method-to-a-Burn-COM-Interface-breaking-td7594427.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/3-9-702-Bundle-update-behavior-tp7595761p7595795.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
