Hi thanks for the answers, but they unfortunately don't answer my question.
Is there a reason/rationale behind this patch creation behavior? Or did the patch appliance rules change at some point while the patch creation logic was left untouched? Cheers Jakob ps: apart from specifying which components to include in a patch, we automated that by using the original files to create the updated installer, and just replace the libs of which we touched the code (we mustn't forget to set a higher file version, of course). It takes responsibility from the devs to know about components and installer/patching etc. Most don't care, unfortunately. Still, it looks to me as if we are going to great lengths to get a patch built in a way so that it doesn't carry already deployed libraries, which differ only by the teeniest amount on the binary lvl. On Wed, Jun 24, 2015 at 6:51 PM David Watson <dwat...@sdl.com> wrote: > If you allow the tools to decide what is in your patch it ultimately does > a binary comparison to see what has changed between versions and includes > them if there is any difference. > > You would need to dig into the patch building tools to implement an > override of this behaviour to examine the version resource of versioned > files. > > I added a feature-request for this a while ago but never managed to find > any time to submit (or write for that matter) an implementation of it. > > For now I author my patch.wxs files with explicit component refs and > control exactly what goes in each patch. > > Dave > > > [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.png] > <www.sdl.com/> > www.sdl.com > > > SDL PLC confidential, all rights reserved. If you are not the intended > recipient of this mail SDL requests and requires that you delete it without > acting upon or copying any of its contents, and we further request that you > advise us. > > SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207. > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 > 7DY, UK. > > -----Original Message----- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: 24 June 2015 17:01 > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] Why does a patch build include same versioned > dlls? > > See https://msdn.microsoft.com/en-us/library/aa368599.aspx > > Palbinder Sandher > Software Platform Engineer > T: +44 (0)141 945 8500 > F: +44 (0)141 945 8501 > http://www.iesve.com > > Integrated Environmental Solutions Limited. Registered in Scotland No. > SC151456 Registered Office - Helix Building, West Of Scotland Science Park, > Glasgow G20 0SP Email Disclaimer > > > -----Original Message----- > From: Jakob Ziegler [mailto:subscr...@gmail.com] > Sent: 24 June 2015 15:20 > To: wix-users > Subject: [WiX-users] Why does a patch build include same versioned dlls? > > Hi > > it always bugged me, that creating a patch either with wix or with the > msimsp patch creation includes dlls which are binary different, but have > the same version (or where the upgraded installer has a lower version). > > When said patch is installed on top of the targeted product, those dlls > will not end up on the system, if I understand things correctly, because > the windows installer will actually compare both versions, not the binary > hashes. > > Is there a reason/rationale behind this patch creation behavior? I failed > to find one. > > Thanks > Jakob > > ------------------------------------------------------------------------------ > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors network > devices and physical & virtual servers, alerts via email & sms for fault. > Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors network > devices and physical & virtual servers, alerts via email & sms for fault. > Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > This message has been scanned for malware by Websense. www.websense.com > > ------------------------------------------------------------------------------ > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
