[wix-users] dependent inistalls and use tracking

[Wesley Manning]

Also are you doing an upgrade on older versions or installing the products on a clean machine?  If an upgrade then the majorupgrade element would affect things as well: http://wixtoolset.org/documentation/manual/v3/xsd/wix/majorupgrade.html.  See the Schedule attribute.

Wes

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Wesley Manning
Sent: March-09-16 2:16 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] dependent inistalls and use tracking

Sorry by GUI I mean GUID.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Wesley Manning
Sent: March-09-16 2:15 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] dependent inistalls and use tracking

I don't know merge modules or tomcat but can speak in general. I don't think you need to be using merge modules for the common portion. Merge modules are kind of an old technology and temperamental from what I read on here.

I'm assuming you have two MSI packages for A and B and they share components for C (i.e. tomcat). I would just put the shared tomcat files in a separate wix file and reference it from your A and B projects. As long as the GUI and install path are the same for each component you install then it should up rev the reference count and not reinstall the components. Do you have custom actions that you run as part of installing tomcat?

Wes

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Lewis Henderson
Sent: March-09-16 10:12 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] dependent inistalls and use tracking

Hi Folks,

I asked a similar question a few days ago and got no response, so I'll ask again with a little more concrete situation.

I have two product installs that both require an apache-tomcat install.  I have no control of which product will be installed first, or if both will be installed.  What I need is for both installs to be able to do an initial tomcat install, or if its already installed, not to install again (as that would overwrite the previous configuration settings).  However, on uninstall, tomcat can't be removed until both products are removed, no matter which installed it in the first place.

I have tomcat coded as a merge module which works fine for uninstall, but the second install does re-install tomcat and therefore wipes out the original configuration settings.

I haven't delved into bundles, but the product installation UI's are pretty complicated, and tomcat may only be installed if certain features of one of the products is selected.  Can a BA handle this kind of complexity?

In any case, I need help to find a solution to this kind of situation.  Please help me out here.  Thanks.

                                                                Lewis Henderson
                                                                OpenText, Inc.

PS: Yes, I need both products to use the same tomcat instance.


____________________________________________________________________
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/