I should add there is some forward planning required as you have to add a detect guid in the main bundle. Technically you can use the main bundle upgrade code as the patch guid. But I found bug where in certain cases it wouldn't work correctly (at least for addon bundles). That reminds me, I have to contribute a test case for that issue.
-----Original Message----- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: October-31-13 11:39 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn Question The patch attribute goes in the patch bundle with a unique guid. Then add a detect attribute to main bundle with detect. I never did a patch bundle but I do use addon bundles and that's what you do. Wes -----Original Message----- From: Christopher Painter [mailto:chr...@iswix.com] Sent: October-31-13 9:49 AM To: General discussion about the WiX toolset.; General discussion about the WiX toolset.; General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn Question I've also found the RelatedBundle element with the Patch action attribute but it's not clear to me how to make the relationship. (I'm still getting two entries in ARP.) Also, am I correct in predicting that when implemented correctly that the removal of a patch will not only uninstall the v2 of B.MSI but will also instruct the parent bundle to reinstall the original v1 of B.MSI and in effect being a removable patch? If so, that's really impressive. ---------------------------------------- From: "Christopher Painter" <chr...@iswix.com> Sent: Thursday, October 31, 2013 7:34 AM To: "General discussion about the WiX toolset." <wix-users@lists.sourceforge.net>, "General discussion about the WiX toolset." <wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] Burn Question Rob, Regarding #2, what makes a bundle a "patch bundle"? Is this something to do with the UpgradeCode, Tag and/or ParentName attributes on the Bundle element? I don't usually ask for samples but if someone could kick me into the right direction, I would greatly appreciate it. I'll be working on it myself but I think I'm stumbling in the dark at this point. Thanks, Chris ---------------------------------------- From: "Rob Mensching" <r...@robmensching.com> Sent: Wednesday, October 30, 2013 1:14 PM To: "General discussion about the WiX toolset." <wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] Burn Question Yes. Two options one does as you describe, the other maybe less so (but might work better): 1. Bundle v1.1 is an upgrade of v1.0. Bundle v1.1 will need to know about the other 19 packages but you don't have to ship them. Burn will skip all the stuff that is already present on the machine. However, you'll want to consider the case that if something goes wrong and one of the original packages goes missing, Bundle v1.1 will need some way to find it (or tell Burn to ignore it, but not sure what that means for your app). 2. Bundle v1.1 is a patch bundle that registers in "Installed Updates". It won't show up in main ARP, it'll show up in the "other ARP for updates". Here Bundle v1.1 only has to take care of that which it owns and all operations (repair/uninstall) on Bundle v1.0 will also be applied to Bundle v1.1. -----Original Message----- From: Christopher Painter [mailto:chr...@iswix.com] Sent: Wednesday, October 30, 2013 6:51 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Burn Question I would like to know if Burn could handle the following scenario. Consider the old pre-burn WiX single MSI distribution. Now consider the way it is today with small micropackges for wix, votive, sdk and son on. Now imagine the sum of those packages 1GB are call it the Big product. Let's say I chunked "Big" into a couple dozen micropackages. Could Burn support a story: Release 1.0: ( Full Download - Not Web Download ) 1GB Chain together 24 packages and present a single entry in Add/Remove Programs for uninstall Release 1.1 ( Full Download - Not Web Download ) 50MB Complain if 1.0 is not installed Chain 5 packages and perform a major upgrade on each of them Present a single entry in Add/Remove Programs for uninstall that removes all 24 packages ( 19 from 1.0 and 5 from 1.0 ) If burn can't do this, I'd love to hear alternative design suggestions. One approach would be that 1.1 is a web download installer that contains all 25 packages but will only download 5 of them. I'm not sure if "Big" product will buy into this or not though. Thanks, Chris ---------------------------------------------------------------------------- -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
