We've decided to go with the approach you've suggested, and I will look into delta patches to reduce the patch size (although since most of our changed files will be videos, I would guess deltas wouldn't help much).
As far as each patch superseding the last, is this something we need to specify in the xml or is it just based on the "base" MSI we use when building the patch transform (i.e., version 5.0.2 would supersede version 5.0.1 just because we built 5.0.2 as a diff from 5.0; or we need to specifically say that 5.0.2 superseded 5.0.1)? As far as chaining patches together, we are having a small issue (or maybe it's working as designed). We have version 5.0 of a bundle with three MSIs installed initially. We are trying to release version 5.0.1 which consists of two MSPs. After installing, we see version 5.0.1 of the patch in the Installed Updates control panel, but in the Programs and Features control panel (uninstall a program) we see version 5.0. Is this by design? When doing testing of the MSIs and MSPs (installing them directly as opposed to bundling them), I see what I would expect - in both control panels version 5.0.1 is displayed, and when the 5.0.1 update is removed, the Programs and Features control panel goes back to showing 5.0. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-strategy-tp7591585p7591676.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
