Actually, it's best if everything that might get patched gets authored into its own fragment. If you patch whole fragments, pretty soon the MSP file is nearly as big as the MSI--defeats the purpose.
-- John Merryweather Cooper Jack Henry & Associates, Inc. (Premier Tech, Inc.) Build & Install Engineer - jXchange Office: 913-341-3434 x791011 jocoo...@jackhenry.com -----Original Message----- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, July 26, 2011 4:14 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Question on Patch Files. Normally a patch just includes resources that have changed, plus any changes from earlier patches - "Patch families can only grow". As far as I know, when you refer to a resource in the patch family, the whole fragment that the resource belongs to is pulled into the patch. Therefore you could refer to just one thing in each fragment that you want in your list and you'd not need to change it in future. I would examine the resulting patch to see how much it has included - I don't know if unchanged resources have any effect on the patch although I'd assume not. You'll likely have to edit your patch wxs every time to change the patch display name, client patch ID etc although these could be automated. -----Original Message----- From: Brian Lemke [mailto:brian.le...@apihealthcare.com] Sent: 25 July 2011 23:22 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Question on Patch Files. When building a Patch for a setup should a patch file contain all items that could change or just the ones I know that have changed. For example I have the following defined: <PatchFamily Id="SoftwareUpdates" Version="$(var.PublicVersion)" Supersede="yes" ProductCode="{11111111-2222-3333-4444-555555555555}"> <PropertyRef Id="ProductName"/> <ComponentRef Id="RegistrySettings" /> <ComponentRef Id="File1" /> <ComponentRef Id="File2" /> <ComponentRef Id="File3" /> </PatchFamily> The two setups I have only differ by one file, say File1. Should I only have in the patch file the components that I know are different? Does it hurt to put these other components in the patch file even if they don't change? I was asking because would it make sense to perhaps have one patch file with everything that could be patched listed in it so I don't have to create this file over and over again? --Brian This message (including any attachments) contains confidential and privileged information intended for a specific purpose, and is protected by law. If you are not the intended recipient, you must delete this message and any attachments. You are hereby notified that any disclosure, copying, or distribution of this message, or any attachments, or the taking of any action based on it, is strictly prohibited. Opinions, conclusions, and other information in this message that do not relate to the official business of API Healthcare Corporation (API Healthcare) shall be understood as neither given nor endorsed by API Healthcare. API Healthcare Corporation 1550 Innovation Way Hartford, WI 53027 ----------------------------------------------------------------------------- - Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users 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. ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ 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. ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
