I've updated the MSBuild wixproj template to fix a few nits and use the un-documented Torch MSBuild tool task. You can see it here at:
http://borgsdemons.com/blog/2013/11/08/improved-msbuild-project-for-building-a-wix-way-patch-from-administrative-installs/ -- John Merryweather Cooper Build & Install Engineer -- ESA Jack Henry & Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -----Original Message----- From: John Cooper Sent: Monday, November 4, 2013 8:31 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Creating Cumulative patches with Patch Creation Properties I also have a post with a rough outline of a project to make a patch using admin installs at: http://borgsdemons.com/blog/2013/10/14/wixproj-skeleton-to-make-a-wix-way-patch/ I'll try and update it when I have time. -- John Merryweather Cooper Build & Install Engineer -- ESA Jack Henry & Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -----Original Message----- From: Blair Murri [mailto:os...@live.com] Sent: Monday, November 4, 2013 2:46 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Creating Cumulative patches with Patch Creation Properties I haven’t used PCP/PatchWiz in years because if all the problems PatchWiz caused in the build farms I have to use with most of the projects I have worked on. In this blog post, Peter describes a way to use “Pure WiX” using an MSI not created by WiX: http://petermarcu.blogspot.com/2008/05/wix-patching-something-you-didnt-build.html. I don’t know if all the links would still work, but there’s enough description in there that you should be able to follow it and fit it into the current instructions. However, if you want to use PatchWiz to make cumulative patches, I would recommend that you always increment the Patch Sequence number. Here’s my question you didn’t answer: if you (as a test) install version 2 MSI (not patched), will your new version 3 MSP correctly upgrade it? If not, you will need to determine why before you can fix this issue. Blair From: TimM Sent: Wednesday, October 30, 2013 10:01 AM To: General discussion for Windows Installer XML toolset. I am currently testing the creation of WiX patches using Patch Creation Properties. Now I am trying this over Pure WiX patches because the versions that we will initially be patching have already been released and when they were built they were NOT built to generate the .wixpdb files. So we have to go with admin extracted installs. I create the initial first patch and test out and it works great. Now we are looking at cumulative patches so I updated my Patch.wxs to have UpgradeImage and 2 TargetImage entries. When I apply the original version 2 patch to version 1 it is ok. I then use the new cumulative patch, that contains version 1 and version 2 changes, and apply that to version 1 release and it correctly upgrades to version 3. But if I apply the original version 2 patch to version 1 and then apply new version 3 patch to that it will not do anything. No files are upgraded and it remains at version 2. So what am I doing wrong here??? Here is what the patch.wxs file looks like: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <PatchCreation Id="{1C7DC01C-72AB-4050-A853-CC53FEE72D5E}" CleanWorkingFolder="yes" OutputPath="patch.pcp" WholeFilesOnly="yes"> <PatchInformation Description="Cumulative Update Patch" Comments="Testing Cumulative Update Patch" Manufacturer="SMART Technologies" /> <PatchMetadata AllowRemoval="yes" Description="Cumulative Update Patch" ManufacturerName="SMART Technologies" MoreInfoURL="http://www.smarttech.com/"; Classification="Update" DisplayName="Cumulative Patch" MinorUpdateTargetRTM="yes" /> <Family DiskId="5000" MediaSrcProp="Upgrade" Name="Upgrade" SequenceStart="5000"> <UpgradeImage SourceFile="C:\Temp\1.0\Sample.msi" Id="Upgrade"> <TargetImage SourceFile="C:\Temp\1.2\Sample.msi" Order="1" Id="Target" IgnoreMissingFiles="no" /> <TargetImage SourceFile="C:\Temp\1.3\Sample.msi" Order="1" Id="Target2" IgnoreMissingFiles="no" /> </UpgradeImage> </Family> <PatchSequence PatchFamily="UpgradePatchFamily" Sequence="1.0.0.0" Supersede="yes" /> </PatchCreation> </Wix> Now I did change Order numbers from TargetImage, but that did not help. What should the Order numbers be? I did not make any changes to the PatchSequence entries. Should any of these entries change between patches? Thanks for any help. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-Cumulative-patches-with-Patch-Creation-Properties-tp7590119.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 ------------------------------------------------------------------------------ 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 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. ------------------------------------------------------------------------------ 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 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
