Sure, but if my merge modules components are merged into the package installers components, then a major upgrade of the package, which ended up using a different version of my merge module, would result in the components in my old merge modules being unreferenced and removed if those same components don't exist in the new version of the merge module. I am just verifying if this is the case. More often than not I've been mistaken when dealing with Windows Installer, so wanted to confirm. =)
Also, if I "change" a component in my merge module, in a compatible way, can I include the *new* version of the component (same file name) with the same component id, in the new merge module, and have packages which include my merge module replace the existing file with the new version (thus upgrading the old application, without breaking it, as long as my upgraded component is compatible). On Sat, 2007-06-16 at 10:59 -0700, Bob Arnson wrote: > Jerome Haltom wrote: > > As I deploy new versions of my merge module, and new third parties > > include them, I may be removing and adding new files. These would result > > in the components being removed and the ref count being decreased, > > correct? In which case, upgrading a third party from library Version A > > to library Version B, might result in the removal of some files from > > Version A. > > > > A merge module can't cause components to be removed. Only the product > determines that, such as by using a major upgrade to uninstall the prior > version (removing components) and installing the new one. > ------------------------------------------------------------------------- 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
