We are moving our software project from the practically auto-creating Visual Studio Installer in Visual Studio 2010 to a WiX installer.  I'd like to use this change to make sure things are right.The application is a subsidiary to our company's main app that will already be installed in its own folder.  The main app has a lot of dlls, some of which the subsidiary app needs to load to work.With the previous installer, the required dlls are pulled into the project and included in the subsidiary app's installation folder.  However, this seems to create possible problems:Multiple versions of the same dll creates confusion, especially if weproduce another app in the future.If the version of the main appchanges, the updates are missed by the subsidiary app.I'm not comfortable with adding our app to the same folder, because they are developed and maintained by different groups.Instead of this, perhaps I could add the path of the main app to the PATH environment variable.  Would this work, and are there concerns with doing this?Is there some other way to approach this issue?
Sharing dlls in a software deployment
windows;deployment;dll