Locating MSBUILD fails if multiple installed versions match version range about gradle-msbuild-plugin HOT 4 CLOSED

hi @freudi74

the plugin doesn't really support a version range when specified in the msbuild version
as per code if the version is not specified it take the latest already which should suit most of the use case
what is the reason behind having both version range in the build.gradle while couldn't just use latest?

from gradle-msbuild-plugin.

• the plugin doesn't really support a version range when specified in the msbuild
  Basically, it does ... it just fails if multiple installations are in that range are found. At least in terms of VS2015 and newer (when the VSWHERE path finds a version).

• what is the reason behind having both version range in the build.gradle while couldn't just use latest?
  There are many good reasons to lock down to a certain version range. For example, the code might build with VS 2017 and VS 2019 ("[15.0,17.0)"), but we want the build to fail if only VS 2015 is installed, because it would fail anyways or produce undesired results. We also don't want to use untested newer versions of VS to build unless we "allow" them in the build script.
  Another example would be I only want it to build with VS 2017, but neither VS 2015 nor VS 2019 ("[15.0,16.0)")

from gradle-msbuild-plugin.

thanks for your explanation

from gradle-msbuild-plugin.

Fixes in bccd066

from gradle-msbuild-plugin.