[WiX-devs] [ wix-Bugs-1457697 ] No way to specify File Sequence when using MergeModules

[SourceForge.net <no...@so...>]

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: Open
Resolution: None
>Priority: 8
Submitted By: thewindprog (thewindprog)
Assigned to: Nobody/Anonymous (nobody)
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-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