We don't use minor upgrades. We do patch, but in practice patches always involved versioned assemblies.
We also use very conservative Major Upgrade scheduling where the old product is entirely removed before the new product is installed. This means I have to work harder to migrate settings from config files, but this effort has been worthwhile as major upgrades have gone off without a hitch. Since the versions in all of our versioned assemblies we build are incremented every build, most of the time the assembly used as a CompanionFile is incrementing upwards build-to-build. Files are still in individual Components and the otherwise unversioned files have their own GUIDs when they have a CompanionFile. I do have one installer that is multi-instance (up to 16 instance transforms), but it also does not contain any unversioned files. It's actually a multi-pass bootstrapper for the main product, so it's definitely a one off. -- 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: tyler.w.r...@accenture.com [mailto:tyler.w.r...@accenture.com] Sent: Thursday, August 29, 2013 9:28 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Component Rules @John Ludlow: Ok I was following what I found in a wix email chain by Chad Peterson from 2011. The post is below as well as the url to the entire email chain. Another option is to use the <RemoveFile/> element tied to the same Component as your <File/> element. This will always clear out the existing file prior to the current install writing the new one. Works for rollback and uninstall. <Component Id="Filetxt" DiskId="1" Guid="<someguid>"> <RemoveFile Id="Remove_Filetxt" Name="File.txt" On="install" /> <File Id="Filetxt" Name="File.txt" Source=".\data\File.txt" /> </Component> The RemoveFiles action is always scheduled before the InstallFiles action by default, so as long as you don't change that sequence in InstallExecuteSequence then it should work fine. I consider this the functional equivalent of the InstallShield "Always Overwrite" setting. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-wix-how-to-always-overwrite-a-file-td6904118.html @John Cooper: I am thinking we had some troubles with multi instance and companion files in the past and have since removed them all from any of our installs, but I wasn't around for that conversation and nobody seems to remember why so I will give that a try thank you. Speaking of that though would that violate the Component rules for a minor upgrade? Tyler Reid | Operations and Infrastructure | Accenture Software | P&C Insurance 1807 Jones Street | Bolivar, MO 65613| USA Office: +cc.xxx.xxx.xxxx | Fax: 417.777.3792 E-Mail: tyler.w.r...@accenture.com<mailto:tyler.w.r...@accenture.com> | www.accenture.com/pcsoftware<http://www.accenture.com/pcsoftware> ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&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. ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
