Joe, we are just looking at patches and I have a question about this method if you don't mind?
I am just testing out with using the sample 'Using Pure WiX' example and I am looking at the PatchFamily element and noticed that you have to add a reference to a component in your main install project. And then you mentioned that you added a new file so in the 2nd patch added the reference to the new component. So my question is do you have to add a reference to all components that changed or do you simply have to add a reference to any component that resides in your target project and then the patch will pick up all changed/updated components? The reason I ask is because in doing the example the sample.txt file updated fine, so I added some .exe files to the sample target and update projects, some that changed and some that did not and I left the ComponentRef in the patch.wxs to still be the same. Did not add any more references. I then built the patch and when I ran it over the target install it correctly upgraded all files that were updated and left all the ones that were the same as is. So it seems to work that way. So was that just a side effect and it was not suppose to do that or is that how it is supposed to work? I have not tried to create a cumulative patch from this example, but if it does work this way then for a 2nd and 3rd patch would you have to add more component references or simply build the cumulative patch and it would only be new components that you would have to add as references? Oh and that does bring up the question on how you built the cumulative patch? what command line do you use to build with to generate the patch to work over 1 and ver 2, and so on? Thanks for any insight that you can supply. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590098.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
