In order for the in-the-box EFTools.msi -- the one that shipped with Visual Studio 2012 and Update 1 -- to detect newer version of the product, the newer version must be between '11.1.21009.00' and '12.0.0'.
The current OOB msi's version is '12.0.0.0' which is greater than '12.0.0'. As a result, when you repair an install of Visual Studio 2012, instead of skipping the install of EFTools.msi, it installs the older version over the top of the newer version. There are two entries in Programs and Features, and an error dialog appear when opening Visual Studio.
One option we have is to always keep the Dev11 msi's version between '11.1.21009.00' and '12.0.0'.
Comments: __Update:__ This may be affected by VS Updates as well. Steps are as follows: 1. Install VS2012 RTM 2. Install OOB EFTools.msi with version > 12.0 3. Install VS Update 1 I will be testing this scenario to be sure, but I suspect that VS Update 1 will install the old EFTools.msi on top of the new one, causing 2 entries in Programs and Features and an error dialog when opening VS.
The current OOB msi's version is '12.0.0.0' which is greater than '12.0.0'. As a result, when you repair an install of Visual Studio 2012, instead of skipping the install of EFTools.msi, it installs the older version over the top of the newer version. There are two entries in Programs and Features, and an error dialog appear when opening Visual Studio.
One option we have is to always keep the Dev11 msi's version between '11.1.21009.00' and '12.0.0'.
Comments: __Update:__ This may be affected by VS Updates as well. Steps are as follows: 1. Install VS2012 RTM 2. Install OOB EFTools.msi with version > 12.0 3. Install VS Update 1 I will be testing this scenario to be sure, but I suspect that VS Update 1 will install the old EFTools.msi on top of the new one, causing 2 entries in Programs and Features and an error dialog when opening VS.