Bugs item #1457697, was opened at 2006-03-24 04:05 Message generated for change (Comment added) made by derekc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1457697&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: candle Group: None >Status: Closed >Resolution: Rejected Priority: 8 Submitted By: thewindprog (thewindprog) >Assigned to: Derek (derekc) Summary: No way to specify File Sequence when using MergeModules Initial Comment: Let us suppose, that the project consist of two parts: merge module "Utils.msm" and main part "Main", main part includes "Utils.msm". Main project builds, the result is "Product.msi" version 1.0.0. Suppose than than new file added into "Utils.msm" merge module. After this, main setup is built, the result is "Product.msi" version 1.0.1. As the result, it is impossible to build patch package from 1.0.0 to 1.0.1. MS SDK states that in order to patch package be valid, "...do not change the order of files in a cabinet". With Wix, this is no opportunity to satisfy this requirement. File/@PatchGroup is ignored when building merge module, and there no other menas to control File.Sequence value. Patch package built in this way, leads to error 1334 during applying (Error 1334. The file 'xxx.xxx' cannot be installed because the file cannot be found in the cabinet file 'yyy.cab'. This could indicate a network error reading the cdrom, or a problem with this package.") Is there any way to deal with it ? ---------------------------------------------------------------------- >Comment By: Derek (derekc) Date: 2006-04-27 23:32 Message: Logged In: YES user_id=518766 Upon further review, this is even more complicated - we'd have to provide a way to assign individual files from the merge module to a different DiskId (a new disk id to avoid disturbing the sequencing of other media). Of course, that further assumes that the merge module is authored with the new file(s) in a separate component to avoid breaking component rules. Please consider using wixlibs instead of merge modules. This allows you use the PatchGroup attribute and avoid the problem altogether. The scenario seems very dangerous in terms of creating a valid and safe patch. Unless we get more requests for this feature, it seem like something we shouldn't support directly. ---------------------------------------------------------------------- Comment By: Derek (derekc) Date: 2006-04-07 00:10 Message: Logged In: YES user_id=518766 There is currently no solution for this that I'm aware of (adding an entire merge module in a patch is a little unexpected since a patch really shouldn't do anything more than update the files in the product - otherwise its an upgrade). However, it sounds like we might need to support something like Merge/@PatchGroup to allow the merge module's files to come late in the sequencing. Does that sound like it would solve this scenario? Please note that if we do this fix, it will be in WiX 3.0 only since it would be a disruptive change. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1457697&group_id=105970 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
