FYI - I have confirmed (using a different project which has not been changed for some time) that when the bundle is built using wix 3.8.1128 it does not have the behavior observed when the bundle is compiled using 3.9.702. Specifically:
Bundle A (built using 3.8.1128) Bundle B (built using 3.9.702) Bundle C (built using 3.9.702) Bundle D (built using 2.9.702) Bundle A on local test system installed. Then either do update to later build, or do uninstall and launch install again. (Two different test cases, with similar behavior.) Bundle B installed as result of 'update' when Bundle A was launched. Uninstall Bundle B. Launch Bundle A, update to Bundle C (posted to web after Bundle B was installed (or uninstalled). Expected result, in that it did not reinstall Bundle B as 3.9.702 code is doing. Start over, but start at Bundle B (which is same code as Bundle A, but compiled with Wix 3.9.702) Bundle B.exe is downloaded to local box. Installed (and uninstalled or left installed to test update. Two similar test cases.) Launch Bundle A.exe (with Bundle D available on web site. DetectUpdate detects Bundle D. Related Bundles and Forward-Compatible detect Bundle C. Bundle C gets installed instead of Bundle D, which is the expected behavior. In all cases above the mba does not have a handler relate to ForwardCompatible. I am not sure if I should be implementing something to get the Wix 3.8 behavior. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/3-9-702-Bundle-update-behavior-tp7595761p7595801.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
