maxmustermann/dotnet-core
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Merge pull request #2581 from KathleenDollard/vs-sdk-issue

Browse source 
Document the VS SDK 2.2.2nn issue
This commit is contained in:
Lee Coward 2019-04-12 15:37:03 -07:00 committed by GitHub
parent 8c1dcf3552 3dd7ad25e5
commit 4a61646026
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
release-notes/2.2/2.2-known-issues.md
View file

@ -26,3 +26,21 @@ to the following ...
<AspNetCoreModuleName>AspNetCoreModule</AspNetCoreModuleName>
</PropertyGroup>
```
## .NET Core SDK 2.2.2nn and 2.1.6nn do not work with Visual Studio 2017
.NET Core SDK 2.2.2nn and 2.1.6nn do not work with Visual Studio 2017. For example, 2.2.203 and 2.1.603 cause failures in Visual Studio 2017. To work on projects in Visual Studio 2017, use .NET Core SDK 2.2.1nn and 2.1.5nn, such as 2.2.106 and 2.1.506. You can install any combination of these SDKs side by side.
You can find the SDKs on you machine using the following at a command prompt:
```bash
dotnet --list-sdks
```
### Visual Studio 2017 can't target .NET Core 2.2
If you receive the error message in Visual Studio 2017:
`The current .NET SDK does not support targeting .NET Core 2.2. Either target .NET Core 2.1 or lower, or use a version of the .NET SDK that supports .NET Core 2.2.`
If you downloaded the .NET Core SDK 2.2 between April 2 and April 12, 2019, the main [.NET downloads page](https://dotnet.microsoft.com/download/) included only 2.2.2nn. Starting April 12th, a new button marked "Compatible with Visual Studio 2017" is provided to target 2.2.1nn. If you downloaded 2.2 prior to this date, and you use Visual Studio 2017, install the compatible version.