MSI installer calling another MSI installer in silent mode using WiX

Ok pretty simple mate, you just need to add the customInclusionList project to your solution. see this link for VSTO 3.0 i think (haven't started on 4.0) its the same for 4.0

You'll need to add the IncludionList output to the setup project and there are some steps for adding the RSAKey value from the primary projects .VSTO manifest to the installerclass code then making sure you add the inclusionlist output in the setup project to each of the "states" Install, rollback, uninstall, etc. read the link it makes more sense than i do... http://msdn.microsoft.com/en-us/library/bb608607.aspx

Also note that if you decide to deploy via MSI instead of clickonce, and you install to Program files (as admin, for instance using SCCM or similiar mechanism) you are Automatically granted Full Trust. this could be another way around your problem...

First all, you shall fix your upgrade code:

<?define ProductVersion = "0.0.2.3"?>
<?define UpgradeCode = "PUT-GUID-HERE"?>

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">

<Product Name="Asd" Language="1033" Version="$(var.ProductVersion)" Manufacturer="Me" Id="*" UpgradeCode="$(var.UpgradeCode)">

Note that the product code is recreated each time you build the installation (by not using the GUID but the asterisk).

The fundamental information is the product version and the upgrade code. The product code identify the specific deployed release, while the upgrade code identity the product releases "family". Softwares having the same upgrade code can be switched with each other. Softwares having the same product codes cannot be installed toghether.

Here is the trick to make upgrade you software:

<Upgrade Id="$(var.UpgradeCode)">
    <!-- Detect older product versions -->
    <UpgradeVersion OnlyDetect="no" IncludeMinimum="yes" IncludeMaximum="yes" Minimum="0.0.1" Maximum="$(var.ProductVersion)" Property="PREVIOUSVERSIONSINSTALLED"/>
    <!-- Detect newer product versions -->
    <UpgradeVersion OnlyDetect="yes" IncludeMinimum="no" Minimum="$(var.ProductVersion)" Property="NEWERVERSIONDETECTED"/>
</Upgrade>
    <!-- Exits successfully in the case newer version are already installed -->
<CustomActionRef Id="WixExitEarlyWithSuccess"/>

By using the above markup, you say to Wix abort installation when he find a product having the same UpgradeCode but the installed one has a Version greater than the current one, but begin the installation (upgrading the current one) if he find a product having the same UpgradeCode and the installed one has a Version less than the current one.

The IncludeMinimum and IncludeMaximum shall do the trick, allowing the upgrade to skip the current version.

Wix doesn't install the same product: you shall be sure that the product code is the same for installed software and MSI-packaged software: if they are different, they are different deployed softwares. Beyond this, if the product has the same product code of the MSI, the installation offers the repair/change options: to disable them you have to play with the Property table of the Wix package, by introducing the ARP_ variables (you can disable repair, change and uninstall, but also setup manufacturer contacts and other properties).

Here is the ARP variable list. I don't know what is their behavior when installing in silent mode, but if you are invoking msiexec from command line, there is a specific repair option to issue repair (/f), so how can it automatically repair your product if you are not requesting?