Use the version lying technique: Change the version of this FileId to 10.1.1 in your patch upgrade image by editing the msi in orca. Then re-build the patch pointing to your edited MSI.
When the patch installs on top of the localised version it won't matter that the transform has removed this attribute in the actual local MSI being upgraded. Patching only looks at the file table version changes at the time the patch was created. I.E. the patch 'thinks': this FileId was version incremented when I was built so i'll happily apply the transform to it. (Make sure your actual file verison matches your edits otherwise you'll get request for source issues on repair). On 15/10/2012 13:03, Uma Harano wrote: > Unfortunately the mst has already been released to our customers. We are now > trying to release the msp patch and it is not patching the file. So we are > trying to see how we can now fix the problem (so that the msp updates the > file correctly) caused by the released mst. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
