We have several .NET based products for which we need to generate multiple MSI files to allow for multiple instances of the same app to be installed on the same machine. For instance, we might have a single server running version of the app that are pointed at either test or QA databases, or may use the same server box to deploy the product for multuple clients. (So, for instance, our web server might have separate installs of the same code in different locations for product names "Client A test", "Client A QA", "Client B Test", etc., where the only real differences are in the web.cionfig files that are not overwritten by the install of a new version.)
Right now we simply have a deployment project for each named variation of the app. This works, but is likely to become a maintenance mess as the number of instances grows. We'd like to be able to maintain only a single deployment project and script the creation of multiple MSIs, one for each product variation, after the build of a baseline MSI.
As I understand it, this should be acheivable by building the MSI, then for each possible instance, making a copy of the MSI and giving it a unique ProductCode and PackageCode; this way Windows should recognize each instance as a unique application. I've done this (as well as changing the produc
View Complete Post