Considering A.MSM with ModuleDependency of B.MSM, when I merge A.MSM into
P.MSI
I notice that WiX does not merge B.MSM into the MSI. This results in the
valiation warning ( really an error )
ICE25 WARNING Possible dependency failure as we do not find
bmm.4cca5793_5d4d_4a83_8652_d89a0c287...@1033 v1.0.0.0 in ModuleSignature table
I've used InstallShield in this scenario for a number of years and it
automatically merges in the dependencies for you. Unfortunatly it's always
done
it wrong in that only 1st order dependencies get their Merge Redirect Folder
associated to INSTALLDIR and all n-th order dependencies are left
unassociated and install to C:\ ( or D:\.... ). I've always had to hack
around this with some post build steps to clean up the directory table.
I'm wondering what the thoughts were on the WiX side to see why decisions were
made the way they were. Based on my experience with InstallShield I always
assumed that the ModuleDependency table was instructive to the build/merge
process and not merely informational.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
