ecsousa / psvsenv Goto Github PK

I'm using the new vs2017 alias, but it doesn't seem to set up the correct path for MSBuild:

C:\> vs2015
C:\> gcm msbuild | select -expand source
C:\Program Files (x86)\MSBuild\14.0\bin\MSBuild.exe
C:\> vs2017
C:\> gcm msbuild | select -expand source
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe

When I run the Developer Command Prompt for VS 2017, the correct version of MSBuild is found:

C:\>powershell -noprofile -c "gcm msbuild | select -expand source"
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\\MSBuild\15.0\bin\MSBuild.exe

Am I doing something wrong?

UPDATE: I was loading the VS 2015 settings in my PowerShell profile, and it appears that the VS 2017 settings don't correctly override the VS 2015 settings (as documented in the steps above). If I load a clean PowerShell instance without first setting the VS 2015 variables, the VS 2017 variables are set correctly. In summary, switching between versions in a single PowerShell instance doesn't appear to be supported, but loading VS 2017 by itself works well.

Just a quick note: it looks like you've updated the script for VS 2019 (85000d4), but there's no mention of this in the readme.