title: MSBuild.exe 15.0 calls cl.exe and link.exe from wrong Visual Studio directory
body: <p>I have two Visual Studio installed on my system: VS 2015 and VS 2017.
  I run msbuild explicitly from the VS 2017 location: </p>
  
  <pre><code>"C:\Program Files (x86)\Microsoft Visual Studio"\2017\WDExpress\MSBuild\15.0\Bin\amd64\msbuild.exe build/binding.sln /p:Configuration=Release;Platform=x64
  </code></pre>
  
  <p>Since I call msbuild from the VS 2017 I expect it to take the tools from VS 2017 as well, but it does not work!</p>
  
  <p>The "normal" Verbosity level shows that msbuild calls C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\cl.exe and C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\link.exe, so it takes them from the older VS 2015 that is wrong.</p>
  
  <p>If I use even more verbose level (/clp:Verbosity=diagnostic) I see that msbuild takes the properties file from the wrong location as well. The message is:</p>
  
  <pre><code>Property reassignment: $(VCInstallDir_140)="C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\" (previous value: "") at C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Common.props (55,5)
  </code></pre>
  
  <p>The indeed properties file is located at C:\Program Files (x86)\Microsoft Visual Studio\2017\WDExpress\MSBuild\15.0\Microsoft.Cpp.Common.props.</p>
  
  <p>The PATH variable is correct and does not contain anything that points to the older VS 2015. The variable VS140COMNTOOLS is unset.</p>
  
  <p>Is it the expected behaviour and how can I tell msbuild to use the tools from VS 2017?</p>