Thanks for your reply, The self-updating bundle seems interesting and I will look more into that.
I understand you advise against swapping out the MSIs on the server. The problem with adding patches as you describe is that we already have our own software that updates the applications we install (it's one of the packages we install, actually). After installation is finished we have a step in our bootstrapper that communicates with this software service to download the latest patches (not only MSPs). Ideally we would not want to update anything (so this updating step should be /very /short). Since we're already downloading the packages, we want them to be the latest. Also, our application is non-trivial in size and scope, which means *a lot* of packages - and a lot of updates and bug fixes. Having to edit the bundle, add the MSPs and updated MSIs and increment the version and rebuild each time we have a new package will take time, time we ideally want to save. It should be noted we don't want to add /new /MSIs. At that point it would seem fair to update the bundle, rebuild and distribute. However, for all the minor versions it just seem like such a hassle. Is there really no way for us to work this way? :) Cheers, Amadeus -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Updating-package-without-rebuilding-tp7582033p7582060.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
