I have CI build system builds an MSI whenever a developer checks in a change. We run automated acceptance tests on the installed MSI.

Basically every MSI is a complete install of the product, so we don't have any versioning (ala Windows installer) per se..

Each MSI has the same product GUID and upgrade GUID, and the same version number. but has a different package GUID (use '\*' in wix).

What I want to achieve is that when the installer runs, it will 'uninstall' any previously installed version of the product, and install the new one.. all from a single MSI (We have a convoluted install process that is out of our control.. citrix and sccm, so we want to give them a simple install path) 

I have tried:

```
<Property Id='PREVIOUSVERSIONSINSTALLED' Secure='yes' />
<Upgrade Id='$UPGRADE_GUID'>  
  <UpgradeVersion Minimum='1.0.0.0'
                  Maximum='99.0.0.0'
                  Property='PREVIOUSVERSIONSINSTALLED'
                  IncludeMinimum='yes'
                  IncludeMaximum='no' />
</Upgrade>

```

and have:

```
<InstallExecuteSequence>
  <RemoveExistingProducts After='InstallFinalize' />
</InstallExecuteSequence>

```

and have tried:

```
<InstallExecuteSequence>
  <RemoveExistingProducts After='InstallInitialize' />
</InstallExecuteSequence>

```

But when I try to install an msi from a subsequent build I get:

```
Another version of this product is already installed. Installation of this version cannot continue. 
To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel. 

```

Which is not really what I was going for..

I understand that I can just update the Version attribute in the product tag, but that becomes difficult to manage. Firstly I can produce 20+ msi builds a day as I have a number of build pipelines that produce MSIs and am not sure how to handle the version numbering in a way that makes sense.

Maybe Windows Installer just does not allow this type of 'always overwrite installed version' install?