If you have the old MSI, there are a couple of options (but I am no expert).
If the old mis supports doing a /a layout then you can extract the files of the old msi to two folder tress, original and changed, change the files in the 'changed' folder tree, and use torch to create a transform. Or you can use orca in the old msi to find out which component the files is associated. Then create a new msi with only all of the files (resources) of that component, using the same component GUID, and run that msi to update the file. But the component must be identical to the component in the original package with regard to the guid, target path, and all resources included in that component. I am just learning and experimenting with a similar situation, so others can provide more expert advice. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-implement-installer-to-update-single-file-Upgrade-Patch-tp7594344p7594346.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
