Hey Stephen, Here is the contents for my sample build.bat file:
@echo call melt.exe to fix the Version 1.0 wixpdb file so that we do not have to worry about original source files/folders. Melt.exe Ver1.0\product.msi -out Ver1.0Corrected\product.wixpdb -pdb Ver1.0\product.wixpdb -x Ver1.0Corrected\Productbits @echo call melt.exe to fix the Versoin 1.1 wixpdb file so that we do not have to worry about original source files/folders. Melt.exe Ver1.1\product.msi -out Ver1.1Corrected\product.wixpdb -pdb Ver1.1\product.wixpdb -x Ver1.1Corrected\Productbits @echo create the transform between product versions torch.exe -p -xi Ver1.0Corrected\product.wixpdb Ver1.1Corrected\product.wixpdb -out patch\diff.wixmst @echo build the patch .msp from differences. candle.exe patch.wxs light.exe patch.wixobj -out patch\patch.wixmsp pyro.exe patch\patch.wixmsp -out patch\patch.msp -t Patch patch\diff.wixmst Oh and I guess if you know the files that are updated then you can probably use the PatchFamiles to reference the components that are changed and need for updating... But if you have a bunch of components then this could get complicated as I was referring to before.... Tim. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Purely-WiX-patching-and-FeatureRef-tp7590049p7590468.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
