Yes, that is the way it looks like we will have to do things. However I would say non-trivial doesn't mean impossible. Someone out there must have thought of this problem before us, otherwise we have a patentable piece of work here in this mailing list :) My name MUST be on the patent!
My hope was to have patches automatically generated by our build system for our release branches based on our RTM version. No human interaction required. -----Original Message----- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: November-08-13 2:28 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Purely WiX patching and FeatureRef The latter. Binary diffs are non-trivial. For example of this, see how TFS handles binary check-ins. Like you, my builds version every rebuilt assembly every build. So, we're guaranteed at least several dozen "new" assemblies every build. Patching without PatchFamily would essentially be just a MajorUpgrade by another name (without the version number change). That's not very useful to us. Hence, we always use PatchFamily and we always specifically select the assemblies to include in the patch. -- John Merryweather Cooper Build & Install Engineer -- ESA Jack Henry & Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -----Original Message----- From: TimM [mailto:timmay...@smarttech.com] Sent: Friday, November 8, 2013 1:16 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Purely WiX patching and FeatureRef Okay Rob, taking out the PatchFamily does allow the patch to all updated files to be correctly patched and therefore does reduce the complexity of this method... Now if we look at Stephen's issue I can see this being a major concern as we also do the same thing where files are updated with version and signing each build and therefore when building the new version all files are updated, but we could have simply a couple files that actually have code changes in them that we want patched. If you knew of all files that were to be patched then yes you could simply place these files into a folder that contained the previous version and have the install built from that and therefore the patch creation would then only see the updated files and correctly patch them, but this is not as easy as it sounds as being install developers we may not know of all the files the developers are updating and the build definitely does not let us know and therefore it would be a pain having to figure out what changed and what only had version/signing changes. So it would be great if there was a setting in the patch.wxs that we can set to only get file binary changes instead of whole files. This way even if we got bit differences of files that only had version and signing differences these would not be big differences and therefore the patch .msp would not be that much bigger than if it had to take whole files. So is there a setting that will allow for just bit differences or will we have to do it the hard way and find the files that are updated and to be patched? Thanks, Tim. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Purely-WiX-patching-and-FeatureRef-tp7590049p7590474.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
