I'm bringing a dead horse back from the grave :) I've gotten a little further in my patching quest. Now I've hit a stumbling block in Pyro.exe (v3.8)
PatchTransform.Validate() is reporting WixErrors.InvalidRemoveComponent My product has thousands of components, my Patch.wxs only lists two(2) components. The strange thing is that the component that is raising this error is NOT listed in my patch file. Anyone have any suggestions? Have a great weekend everyone. Stephen -----Original Message----- From: TimM [mailto:timmay...@smarttech.com] Sent: November-13-13 2:21 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Creating Wix Pure patch with Melt.exe and Pyro.exe fails I have been testing the 2 patching methods for WiX: Using Patch Creation Properties Using Purely WiX I have created basic samples for both and got both of them working okay so I am now try a real install upgrade patch. So I get the .msi and .wixpdb files for say version 1.0 and for version 1.1 Since these files are moved from the original source trees I have to use melt.exe to extract and generate new .wixpdb files so I use the following cmds: Melt.exe "1.0\product.msi" -out "1.0x\product.wibpdb" -pdb "1.0\product.wixpdb" -x 1.0x\Productbits Melt.exe "1.1\product.msi" -out "1.1x\product.wixpdb" -pdb "1.1\product.wixpdb" -x 1.1x\Productbits Once this step is done I trigger the torch.exe, candle, and light.exe commands to generate the wixmst and wixmsp files. Finally I run the pyro.exe -delta on these files to generate the patch and it is at this point it fails with a bunch of PYRO0103 errors. These errors are all referring to files that are missing from the original source directories where they were built from or stored on the build machine. Now these missing files are all binary table entries and merge module .msm entries. So I thought that melt was suppose to do a correct extraction of the .msi's so that the original build folder structure was not needed? Are there any melt or pyro cmd options that are suppose to be used to make sure that this does not occur? Again if we have to retail the exact build folder structure for the release builds and the builds that will be used for creating a patch then it will be a pain to maintain.... Has anyone ran into these kind of Pyro errors and if so what did you do to solve the issue? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-Wix-Pure-patch-with-Melt-exe-and-Pyro-exe-fails-tp7590635.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users