Chris Houser (HIS) wrote:
When we build our packages with WiX v3 (build 3526) the custom actions
in the ModuleInstallExecuteSequence table of one of the merge modules
is not being merged correctly into the InstallExecuteSequence table of
the main package. The custom actions are ending up with the sequence
number from the MSM, instead of relative to the standard actions. As
a result some are ending up after InstallFinalize. We do not own the
MSMs so would rather not make updates to them.
Do the standard actions in ModuleInstallExecuteSequence exist in the
.msi before being merged in? The doc says:
If the sequence number in the merge module differs from that for the
same action in the .msi file sequence table, the merge tool uses the
sequence number from the .msi file.
I'd expect it to work but then the linker lets mergemod.dll do all the
heavy lifting of merging modules, so it's a bit of a black box. Or a
big, huge black box.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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
