Sounds like the 1.0 & 1.1 MSI's have different Product Codes. Did you implement major upgrade functionality for 1.0 MSI -> 1.1 MSI? I had this exact same problem as I'd released v1.0 & v1.1 of a product with the same Product Code then released v1.2 with a different Product Code so I could add major upgrade support. When I recently had to release v1.3 I found problems trying to generate patches.
I build patches using the msimsp/patchwiz method not the WiX only method so the following may not work or may need tweaking for WiX only patch building. You'll need 2 versions of your 1.2 MSI, one for each product code. You can simply create one & then modify a copy of it using something like InstEd or Orca (you will need to make sure they both have unique package codes too, just regenerate it for the one you're modifying). Once you've done that create a second PatchFamily for the 1.1 MSI -> 1.2 MSI & it should generate a single MSP which does both updates. However if you then need to patch to 1.3 for example you'll need to continue supporting 2 Products in this manner. This behaviour is by design. If you want to use patches (small update/minor upgrade in Windows Installer terminology), don't change the Product Code. If you want to use major upgrades you need to change the Product Code. See -> http://msdn.microsoft.com/en-us/library/aa370579.aspx Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** 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: Richard Horsley [mailto:richard.hors...@eicltd.com] Sent: 25 March 2010 09:32 To: wix-users@lists.sourceforge.net Subject: [WiX-users] MSI patching for two versions of the same MSI? I have a WIX patch that I need to apply to all client PC's with a particular product installed. I generated the original MSI and have the WIX script that was used to create it. The process has gone like this: MSI installer v1.0 created and distributed to 50% (ish) of client machines. MSI installer v1.1 created and distributed to other 50% of machines at a later date. MSP patcher v1.1 created to patch all original 1.0 installations to 1.1. MSP patcher v1.2 created with intention of patching all version to v1.2 The issue is this: The 1.2 MSP will install fine on clients with the 1.0 MSI, and clients who have 1.1 installed, as long as they were installed with the 1.0 MSI and then PATCHED to 1.1 using the MSP. Clients installed using the 1.1 MSI will not patch using the 1.2 patcher. IS there a way of correcting this in my patch file? Or is this behaviour by design? 1.2 Patch.wxs is as follows: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Patch AllowRemoval="yes" Manufacturer="Company" MoreInfoURL="http://www.site.com/"; DisplayName="EDScripts 1.0 to 1.2 Patch" Description="Update to all Scripts files." Classification="Rollup" TargetProductName="ED Scripts Package" > <Media Id="5000" Cabinet="RTM.cab"> <PatchBaseline Id="RTM"/> </Media> <PatchFamilyRef Id="EDScriptsPatchFamily"/> </Patch> <Fragment> <PatchFamily Id='EDScriptsPatchFamily' Version='1.2' Supersede='yes'> <ComponentRef Id="component0"/> </PatchFamily> </Fragment> </Wix> Help is much appreciated! Richard ________________________________ ######################## DISCLAIMER #################### Please consider the environment before printing this e-mail. This e-mail has been scanned for all known virus's but this is not a confirmation it is virus free. This is an e-mail from EIC Limited (Company Reg: 1086295). The contents of this e-mail are confidential. EIC Limited do not accept responsibility for the accuracy or completeness of the contents of this e-mail as it has been transmitted over a public network. If you receive this e-mail in error please accept our apology. If this is the case we would be obliged if you would contact the sender and then delete this e-mail. THIS E-MAIL AND / OR ANY REPLIES TO IT, AND ANY ATTACHMENTS MAY BE INTERCEPTED, COPIED OR MONITORED BY EIC LIMITED FOR THE PURPOSE OF MONITORING OR KEEPING RECORD OF ITS BUSINESS AND FOR THE PURPOSES SET OUT IN THE TELECOMMUNICATIONS (LAWFUL BUSINESS PRACTICES) (INTERCEPTION OF COMMUNICATIONS) REGULATIONS 2000. All statements made in this e-mail are subject to contract. The contents are not to be regarded as a contractual offer or acceptance. The sender is not authorised to bind EIC Limited. The views expressed in this e-mail are those of the sender and not necessarily those of EIC Limited. ######################## DISCLAIMER #################### ------------------------------------------------------------------------ ------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
