> That level of control isn't possible in a merge module. Provide an .msi > package instead.
So, what's the point of merge modules then? If I can't distribute a third party library that other people can use as a dependency, what good are they for? And I don't think one can reasonable say it can be used as a dependency if two consumers installs will conflict. If I provide a .msi file, how will their .msi file include it? ------------------------------------------------------------------------- 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 WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
