Rory Clark wrote: > What exactly does the Dependency element do? >
Not much. It creates rows in the ModuleDependency table but it's up to consumers of the merge module to provide them. (Some setup authoring tools try to maintain a global list of merge modules and resolve dependent merge modules automatically; WiX doesn't, in favor of explicit authoring.) > My belief, which appears to be incorrect, is that reference counting > should be happening here so that if you uninstall the Extension, the > ExtensionSDK is removed as nothing depends on it, but the > ExtensionLibrary and ExtensionRuntime should both be left behind because > Application depends on it. > > For starters, is this a correct assumption? > No. Merge modules are simply a packaging convenience; once merged, the module's components become part of the consuming product (i.e., .msi). MSI bases all its reference-counting decisions on the component level. In your case, you have two products installing the components from ExtensionLibrary.msm so they get a ref count of two. The other components get a ref count of one so when you uninstall the Extension product, they get uninstalled. What you want to do is add explicit Merge/MergeRef elements for both products. -- sig://boB http://bobs.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
