Menu
EDIT FIX - Reinstalling VS did not work, reinstalling windows then VS did the trick... we live in 2019 almost and this shit is required to get vs to work properly?
I created a .NET Standard Class library which it seems to point to 1.6, when i go to change it to 2.0, I dont see it in the list (see attached image)
Also attached is latest info from my machine and versions, I have installed both the .NET Core 2.2.1 x64/x86 SDKs and I have the .NET Full Framework 4.7.2
EDIT 1: how vs was installed
537
The current .NET SDK does not support targeting .NET Core 2.1. target .NET Core 2.0 or lower or use a vs of the .NET SDK that support NET Core 2.1 Show activity on this post. In general, when new preview version of .NET Core 2.X appears and you are getting the error like this:
However Microsoft saw an opportunity to broaden the compatibility of .NET Standard 2.0 to include .NET Framework 4.6.1, this meant changing the existing Framework support levels for .NET Standard 1.5 and 1.6, as they had already been released.
: VS2017 : Target framework drop down does not show .NET Core 2.1 option The current .NET SDK does not support targeting .NET Core 2.1. target .NET Core 2.0 or lower or use a vs of the .NET SDK that support NET Core 2.1 Show activity on this post.
After searching a lot, we found all .Net Core SDK versions installed (latest till 2.2.10) are 64 bit except one 2.2.301 which is x86 version. Command dotnet --info helped us to find the same.
My team got into this issue. Though we installed all .Net Core SDK but VS2017 targer framework was showing up to .Net Standard 1.6. After searching a lot, we found all .Net Core SDK versions installed(latest till 2.2.10) are 64 bit except one 2.2.301 which is x86 version.
Command dotnet --info helped us to find the same. In dotnet --info output, Base path was pointing to C:\Program Files (x86)\dotnet\sdk\2.2.301\
SDK paths: C:\Program Files\dotnet\sdk
C:\Program Files (x86)\dotnet\sdk
Finally, we uninstalled the x86 version and then the Environment path reset and pointed to 64 bits SDKs as shown in below diagram. Now, targer framework is pointing to .Net Standard 2.0.
114
I just ran into this issue. Reinstalling the sdk and VS didn't help. The issue ended up being an incorrect order of paths in the System Path variable. As soon as I moved C:\Program Files\dotnet\ before C:\Program Files (x86)\dotnet\ VS was able to pickup the correct sdks.
35
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
