.NET Core 2.2 Can't be Selected In Visual Studio Build Framework
Solution 1:
I have same problem. I am trying fix this issue about one day. Finally I figuret out. My VS version is 15.9.11 and Community Edition.
Issue details: 2.1.6xx & 2.2.2xx version of the sdks are only supported on Visual Studio 2019. VS 2017 needs 2.1.5xx & 2.2.1xx versions of the sdk.
How to fix the issue? Install 2.1.5xx version of the SDK if you are targetting a 2.1 app Install 2.2.1xx version of the SDK if you are targetting a 2.2 app.
The link is here
Edit: The direct link to downloadable installers is https://dotnet.microsoft.com/download/dotnet-core/2.2. As noted above, do check which SDK version is compatible with Visual Studio 2019 and/or Visual Studio 2017.
For example, if you want to use .NET version 2.2.7 in Visual Studio 2017 (v15.9), the only SDK version that works is SDK 2.2.109. To use SDK 2.2.206 you must have Visual Studio 2019 (v16.0). To use SDK 2.2.402 you must have Visual Studio 2019 (v16.2).
Solution 2:
Configure Visual Studio 2017 15.9 to use the previews of .NET Core SDK (in Options) and restart VS.
Update in 2019:
Microsoft decides that VS2017/2019 should use different .NET Core SDK versions, so make sure you do install the correct versions for your VS versions, and read the official announcement here,
https://github.com/dotnet/announcements/issues/108
You might find the SDK version/VS version table in .NET Core release notes, such as https://github.com/dotnet/core/blob/master/release-notes/2.2/2.2.4/2.2.4.md
Is a good practice to subscribe to the Microsoft .NET and Visual Studio team blogs so that you can always learn the new things, like https://blogs.msdn.microsoft.com/dotnet/2018/11/13/net-core-tooling-update-for-visual-studio-2017-version-15-9/
Solution 3:
Visual Studio 2017 and 2019 require specific build versions. Missing these will give this error.
- 2017 uses x.x.100
- 2019 uses x.x.200
Latest sdk https://github.com/dotnet/core specific to each vs version.
https://github.com/dotnet/core/blob/master/release-notes/2.2/2.2.4/2.2.4-download.md
- 2017 install 2.2.106
- 2019 install 2.2.203
This resolved the issue