I'm thankful for the tips about WholeFilesOnly set to 'yes'. I had the same experince when it was set to 'no'. Nothing was installed. After changing it to 'yes' the patch worked smoothly!
Thanks! Regards, Oivind Brower, Jason wrote: > > I would agree that this is a problem - but since the contents are > different, the files should be included as part of the msp. In fact > later down in the log it even includes the line: "Including entire file: > 'C:\build\******\latest\.\PFiles\******\bin\******.dll';" Basically, > the file is included but never installed during the patching process. > When you run msiexec for patches, you have the REINSTALLMODE options to > tell windows what to do (i.e. reinstall everything, version > current > version, version >= current version, only missing, etc). > > > > To make things more interesting, I have been using WholeFilesOnly="yes" > for the PatchCreation element in the wxs file. When I change this flag > to no, the files get patched just fine. This technically solves the > problem, but I am still confused as to why... Initially I was being > pessimistic and just including the whole file. How and why does a > binary file patch differ compared to simply including the whole file? > > > > I also have found a bug for the PatchCreation.CleanWorkingFolder > attribute. This maps to the DontRemoveTempFolderWhenFinished value in > the Properties table of the pcp file. If I set CleanWorkingFolder="yes" > then DontRemoveTempFolderWhenFinished becomes 1 when it should be 0 > (values are opposite). > > > > ________________________________ > > From: wix-users-boun...@lists.sourceforge.net > [mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Vitaly > Dolya > Sent: Sunday, June 18, 2006 7:46 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Patching Problem > > > > Brower, Jason wrote: > > I am running into problems when deploying the msp patch files. > Everything compiles properly and the msp is successfully created. > However, dlls that have changed are not installed when the msp patch is > applied. Below is the output generated by MsiMsp and it looks to be > including the dlls. For the cmdline to apply the patch I am using: > > msiexec /update patch.msp REINSTALL=ALL REINSTALLMODE=amus /L*v > c:\patch.log > > [skipped] > > > > WARNING (14): File versions are equal. Upgraded: > 'C:\build\******\latest\.\PFiles\******\bin\******.dll' ver=2.0.47.0; > Target: > > It looks like this is a problem: you should change (increase) file > version to make patch work properly. > NOTE: in a same time you may keep assemblyversion unchanged for .net > assembly, so you don't have to > change all the other assemblies that depends on it. > > > > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://n2.nabble.com/Patching-Problem-tp692530p3661355.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
