My mba which has been working in this regard for about a year, is based on the Wix toolset Setup\WixBA\UpdateViewModel code which implements DetectUpdateBegin and DetectComplete. Some time ago I added some customization to these handlers to allow our build process to place builds into a dev, test, and live area, and allow the mba to detect whether the setup is running on a marked dev or test system and get builds from those staging areas. But those changes have also been working prior to seeing this new behavior.
DetectUpdateBegin spawns worker_DoWork which calls Engine.SetUpdate and return codes. This code is the same as in the wix toolset source. My atom feed document is generated at build time and I only include information for the one build that I intend to post to the web site, so it surprised me that the other intermediate bundles (other than the one the user launched) were still around on the local system to be reused. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/3-9-702-Bundle-update-behavior-tp7595761p7595765.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
