[wix-users] How to fix old broken installs

[Hoover, Jacob]

If you are using Burn bundles, you could make 3 MSI's with the shared bits being in a single shared MSI, and have both ProductA bundle and ProductB bundle include Shared in their chain.

If it's a COM DLL, and everything is in process, you could also consider using registration free COM if ProductA and ProductB can be installed separately.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Charles Gallo [9Dots Management]
Sent: Monday, August 01, 2016 2:01 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] How to fix old broken installs

Thanks
It's basically TWO scrambled DLLs.  The GOOD news is that we are enough in a vertical that when a new version comes out, we can sit with the users, and do a full uninstall of both product A and Product B, then clean installs - I think I can come up with a cleanup program

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Wheeler, Blaine (DSHS/DCS)
Sent: Monday, August 01, 2016 2:31 PM
To: 'WiX Toolset Users Mailing List' <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] How to fix old broken installs

If it is badly scrambled, I would start over with new GUIDs. If you have many shared controls try to use wixlibs first and then consider fragments as a second choice.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Charles Gallo [9Dots Management]
Sent: Monday, August 01, 2016 11:09 AM
To: WiX Mailing List (wix-users at lists.wixtoolset.org)
Subject: [wix-users] How to fix old broken installs

OK, I need some advice

One of the big reasons I'm moving to WiX is we have some broken installs - and in particular, boke DE-installs, all of which were done by my predecessors in Installshield

Well, it turns out, they were installing the same component in multiple installs, but with DIFFERENT GUIDs, so reference counting etc is broken, so if the user de-installs product A that shares a DLL (or registry etc) with product B, we get hosed

So, what is the best way to go forward?  If product A is the main product, and product B required Product A - change the GUIDs in Installer B to match product A (actually, yes, I know fragments etc so they match), or a full set of NEW GUIDs (again with fragments etc) and write off any "old" installs?  Something else?

Charlie




____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/