I have a situation which is similar to the case when a CompanionFile is used but for file removal and not upgrade.
I have a shared location in Common Files where application support dlls that are used by different products are installed. These files are installed with SharedDllRefCount set to 'yes'. Now I have one product that installs an old set of these common files, and then I have a new product that contains the same set + a new required dll. So, Product A: a.dll - v 0.1 b.dll - v 0.1 Product B: a.dll - v0.2 b.dll - v0.2. c.dll - v0.2 (in this case, a & b.dll depend on c.dll) now, i install Product A, followed by Product B - and then uninstall Product B - I will only be left with a & b.dll since c.dll only had a reference count of 1. My question is this - is there any way I can ensure that c.dll only gets uninstalled when a.dll is being uninstalled (again, kind of like CompanionFile by for file removal). Thanks. -- Ali-Akber Saifee ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
