Edwin as you described this is the behavior that is occurring as the ProductCode is different, but the ProductVersion and UpgradeCode are the same.
Are my only options to accomplish what I want to: 1. Create a new MSI with a different ProductCode and UpgradeCode for each Brand. 2. Configure my installer to support Multiple Instance installs. On Thu, Jun 23, 2011 at 11:51 AM, Castro, Edwin G. (Hillsboro) < edwin.cas...@fiserv.com> wrote: > > As I understand from the Wix docs that when the MajorUpdate element is > > used with the attribute AllowSameVersionUpgrades="no" that I should be > > able to run my installer a second time and the new installation would be > > treated by MSI as a new product independent from the previous one. I'm > > not finding this to be the case though. > > This is *not* how I understand the meaning of the > AllowSameVersionUpgrades="no". Windows Installer does not use the Upgrade > table to determine what constitutes an independent product. That is driven > by ProductCode, ProductVersion, and UpgradeCode. The Upgrade table provides > a mechanism for finding/detecting earlier installations and automatically > removing them as part of the current install. The value of > AllowSameVersionUpgrades will only affect whether a related product (equal > UpgradeCode but different ProductCode) will be detected if it has the same > ProductVersion as the product getting installed. > > Assume you install PackageA with some ProductCode, ProductVersion and > UpgradeCode. > > Installing PackageB with a different ProductCode than PackageA and the > same ProductVersion and UpgradeCode as PackageA will not result in > PackageA's installation getting selected for removal. In my experience this > results in multiple entries in ARP (they are different products after all) > but might end up clobbering each other's resources (which is very bad). I > would recommend that you avoid releasing different related products (equal > UpgradeCode but different ProductCode) with the same ProductVersion. > > If you install PackageA once. And then attempt to install it again, then my > experience is that Windows Installer will treat that as a repair situation. > This is the behavior I would expect since it is the same product (same > UpgradeCode, ProductCode, and ProductVersion... and if it really is the same > package, then same PackageCode). > > Edwin G. Castro > Software Developer - Staff > Digital Channels > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > Please consider the environment before printing this e-mail > > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with > vRanger. > Installation's a snap, and flexible recovery options mean your data is > safe, > secure and there when you need it. Data protection magic? > Nope - It's vRanger. Get your free trial download today. > http://p.sf.net/sfu/quest-sfdev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
