As of Visual Studio 2017, you can install multiple editions of Visual Studio (Community, Professional etc) and it requires new way to detect its instances. (See also this and this ).
So the problem for windowslib is that the result from windowslib.visualstudio.detect actually did not quite consider this situation and it uses MSBuild version number as a key to select Visual Studio such as 12.0 and 14.0. You might think we could use 15.0 for VS 2017, but this does not work because we could have multiple installation of MSBuild that have same version number 15.0. So for now we should have a way to choose one instance from multiple installation of Visual Studio 2017 by its name such as Visual Studio Community 2017 RC and Visual Studio Enterprise 2017 RC etc.
So for now output from windowslib.visualstudio.detect is going to look like this:
TIMOB-24189
As of Visual Studio 2017, you can install multiple editions of Visual Studio (Community, Professional etc) and it requires new way to detect its instances. (See also this and this ).
So the problem for
windowslib
is that the result fromwindowslib.visualstudio.detect
actually did not quite consider this situation and it uses MSBuild version number as a key to select Visual Studio such as12.0
and14.0
. You might think we could use15.0
for VS 2017, but this does not work because we could have multiple installation of MSBuild that have same version number15.0
. So for now we should have a way to choose one instance from multiple installation of Visual Studio 2017 by its name such asVisual Studio Community 2017 RC
andVisual Studio Enterprise 2017 RC
etc.So for now output from
windowslib.visualstudio.detect
is going to look like this: