Closed shadowmint closed 7 years ago
There is a specific handling for VS 2017 here which was introduced in #47.
When you provide toolsVersion: 15.0
, it should not look under C:/Program Files (x86)/MSBuild
anymore.
Maybe this helps?
my bad, I've opened this issue on entirely the wrong issue tracker.
Yup, that works for me~
I was using msbuild
not gulp-msbuild
, and that doesn't work.
"auto" option not working correctly with VS2017. I don't think the solution provided here would be the correct one. If I have people in a team working with mixed versions (ie.: VS2015 & 2017), "auto" should be able to find the correct version for each environment, and now it doesn't. I have to manually specify the specific version on each environment when "auto" should be enough, because right now it defaults to 4.0 (like the OP mentioned originally).
Can msbuilder-finder.js be improved to better detect the VS2017 environment? You are already doing the correct thing when you manually specify toolsVersion: 15.0, so you should only modify the code accordingly for the correct detection.
@CesarD thanks, I have released a new version that prefers newer MSBuild-Versions in the auto detection.
Cool, now it works perfectly! Thank you very much!
After installing VS2017, the path to msbuild seems to have changed, resulting in:
This seem to be because its falling back to the windows folder because the latest framework version (15), doesn't have an MSBuild.exe under C:\Program Files\MSBuild\15.0:
This appears to be a new VS2017 issue and frankly after reading the documentation, I'm not actually sure what the correct behaviour even should be, but if you want to track it, there are a bunch of people talking about the issue here:
...for now, I've just uninstalled VS2017 to remove the '15' framework version to get things working again.