To keep File.Sequence consistent with the order of files in the CAB, we make administrative images of both databases and then run the following command on them before executing MSIMSP: WiRunSQL.vbs package.msi "UPDATE `File` SET `Sequence` = 0" "UPDATE `Media` SET `LastSequence` = 0" Because all the File.Sequence values then are 0 in both databases, the transform generated by MSIMSP does not include any File.Sequence changes. Any File rows added by the transform would get File.Sequence = 0 but MSIMSP generates new sequence numbers for new files anyway. If I open the old MSI in Orca and apply the generated MSP to it, the result looks sensible: File.Sequence and Media.LastSequence of old rows are unchanged (as they should, because the old CABs are kept), and new files get larger sequence numbers that refer to the CAB included in the MSP. These results are with MsiMsp.exe 2.0.2600.0 and PatchWiz.dll 2.0.2600.0. I expect this hack would fail if there were multiple CABs with the old MSI and files were added to something other than the last one. Do you see any other problems?
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
