As far as I know, the ModuleDependencies table is only checked by
validation. I don't think the Windows Installer runtime itself checks.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rory Clark
Sent: 22 June 2007 20:40
To: [email protected]
Subject: [WiX-users] Module dependencies
I have a merge module that has a dependency element defined:
<wix:Dependency
RequiredId="unittest_1.0.0.0.07C25BE8_1E39_D890_9A49_A0A1E330948C"
RequiredLanguage="0" RequiredVersion="1.0.0.0" />
When the module is merged into an MSI, I have an entry in the module
dependency:
ModuleID: kenbase_1.0.0.0.49C6F91B_94B1_73FC_410E_8D1110FF1DC3
ModuleLanguange: 0
RequiredID: unittest_1.0.0.0.07C25BE8_1E39_D890_9A49_A0A1E330948C
RequiredLanguage: 0
RequiredVersion: 1.0.0.0
On the target machine, the MSM witht he ModuleID of
kenbase_1.0.0.0.49C6F91B_94B1_73FC_410E_8D1110FF1DC3 has not been installed,
but the installation "completes successfully."
Is there way to make the an installer obey this dependency short of a custom
action?
Thanks!
Rory
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
