-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Unable to determine the correct CMake Generator for Visual Studio" #7324
Comments
[Async Triage]: Seems worth doing and given VS 2017 is still supported something we should do. Doesn't seem like FR unless it's totally blocking. @RussKie can it be assumed you don't want to move to VS 2019? |
VS17 in this case is Dev17, which is unreleased. |
VS2017 is Dev15 |
Ah. In that case, seems like this could wait until the public previews exist. |
I already have a PR with a fix out at #7342 if you want to take a look. I put it out a few days ago. |
Sure, approved. "VS17" is just too ambiguous and we really should just use a non-year version scheme.... |
I also tried VSWhere 2.8.4, and the results are the same. |
Raised microsoft/vswhere#238 |
This seems to work - note the lower boundary is set:
Not sure what the lowest version we want to support though. |
I have VS17 installed, and now trying to build dotnet/winforms from cli fails due to the following error message:
Naively I tried to change Microsoft.DotNet.CMake.Sdk.targets to:
<PropertyGroup> <VSGenerator Condition="$(_HighestCompatibleVSVersion.StartsWith(16.))">Visual Studio 16 2019</VSGenerator> + <VSGenerator Condition="$(_HighestCompatibleVSVersion.StartsWith(17.))">Visual Studio 17 2020</VSGenerator> </PropertyGroup>
But this fails even more spectacularly:
The follow change seems to work:
The text was updated successfully, but these errors were encountered: