I'm having some trouble creating a patch for a real world sized application after having successfully followed the patching "using purely wix" guide within the wix 3.x manual for a small test program.
The error is occurring at the final patch production phase (using Pyro) and I'm getting the following output: warning PYRO1079 : The cabinet 'RTM.cab' does not contain any files. If this installation contains no files, this warning can likely be safely ignored. Otherwise, please add files to the cabinet or remove it. error PYRO0227 : The transform being built did not contain any differences so it could not be created. The patch.wxs xml definitely defines a feature ref that should have changed between the original and the new version of the program; therefore I imagine I am possibly getting the PYRO1079 warning because of the PYRO0227? The patch wxs is fairly similar to the one used for the small test program. Nevertheless here is some background on the environment: . Using Wix 3.0.5419.0 tools . There are no warnings or errors when creating the msi / wixpdb files for the original or updated application versions . http://blogs.technet.com/b/alexshev/archive/2008/03/08/from-msi-to-wix-part- 9-patching.aspx states that having a compression state of no in the package xml element within the wxs for the msi files is important for patching. I have tried both yes and no as I only discovered that article after I had the simple example working and it appears that I successfully patched my simple example with a setting of yes. I'm aware that this article is fairly dated; is compression still relevant to patching? . The changes between the original and the update version of the program can be seen within the msi files using Orca. Files that have changed in the new version have grown in size, have a higher version number and have all been created/modified after the original files. According to http://msdn.microsoft.com/en-us/library/aa368599%28v=VS.85%29.aspx that should be more than enough for the files to be considered as different. . Furthermore I have separately tested the two msi files by installing the applications on a VM and checking the files installed. The original msi has the original files and the update version msi contains the new files. . Both sets of compiled files (original and update) are available at all times including when using pyro. http://sourceforge.net/tracker/index.php?func=detail <http://sourceforge.net/tracker/index.php?func=detail&aid=2086871&group_id=1 05970&atid=642714> &aid=2086871&group_id=105970&atid=642714 implies that not having all the files to hand might cause an issue when pyro is running. Furthermore I have checked the wixmst file output from torch and the relative paths seem correct. Can anyone shed any light on this / point me in the right direction? Thanks, Liam ------------------------------------------------------------------------------ What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
