[wix-users] Cleaning up "worst practices" in shared files

Phill Hogland phill.hogland at rimage.com
Thu Sep 1 12:40:54 PDT 2016

Also consider a wixlib (if both using same version of wix tools), else a merge module.

From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Walter Dexter <wfdexter at gmail.com>
Sent: Thursday, September 1, 2016 2:27:59 PM
To: WiX Toolset Users Mailing List
Subject: [wix-users] Cleaning up "worst practices" in shared files

This is due to lack of communication between teams, not willful stupidity.

Both I and another team have MSIs that install the same two files. Call
them "r1.ini" and "r15.ini".

In my MSI, I have each one in a separate component with unique GUIDs.

In their MSI, both are in a single component with yet another GUID, along
with three more files that I don't deploy.

It's my feeling that we need to get to a point where we both install with
the same GUID so reference counting works, or move the files to their own
MSI that one team "owns" and both teams can then deploy that new MSI.


1. What's the best route to cleaning this mess up?
2. Which going-forward path (separate MSI vs. agreed to GUID) is
preferable? We deploy only via Microsoft system management tools, so
bundles aren't involved.

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

More information about the wix-users mailing list