Hi Wix-users, Another chestnut to do with shared MSM, here's the scenario:
PRODUCT 1 contains: - MSM_A with contains version 1 of a backward compatible, A.dll, in component A, this depends on - MSM_B1 which contains version 1 of a non-backwards compatible, B1.dll, in component B1 PRODUCT 2 contains: - MSM_A with contains version 2 of a backward compatible, A.dll, in component A, this depends on - MSM_B2 which contains version 2 of a non-backwards compatible, B2.dll, in component B2 SCENARIO 1. Install Product 1, this installs A and B1 on the machine 2. No install Product 2, this upgrades A to version 2, and installs B2 on the machine (side by side with B1) 3. Now un-install Product 2, this removed B2 but leaves A with the upgraded version. Using A.dll now FAILS as it required B2, but only has B1 installed. Note that, to complicate matters, the dlls A, B1 and B2 are all COM (which is why Product 1 and Product 2 don't simply contain their own separate versions of A). But I think that this is a slight red-herring, though I may be wrong on this. Suggestions so far have been 1. Make B2 permanent - though this seems ugly, and results in files left on the machine after un-installing all products 2. Remove product 1 when product 2 is installed, which isn't really an option 3. Effectively changing the setup so that B1 and B2 are replaced with an upgrade component B which is upgraded in the same way as A is (though as these are shared, not backwards compatible and COM his make this option none trivial) Any help on this much appreciated. Yours, David ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
