question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The .NET Core SDK cannot be located

See original GitHub issue

Environment data

dotnet --info output: It was not possible to find any installed .NET Core SDKs Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from: https://aka.ms/dotnet-download

Host (useful for support): Version: 3.0.0 Commit: 95a0a61858

.NET Core SDKs installed: No SDKs were found.

.NET Core runtimes installed: Microsoft.NETCore.App 3.0.0 [C:\Program Files (x86)\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.0.0 [C:\Program Files (x86)\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-download

VS Code version: 1.40

C# Extension version: 1.21.6

Steps to reproduce

Expected behavior

VScode find .net core sdk

Actual behavior

VScode can’t find .net core sdk but i installed it 11

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:26 (4 by maintainers)

github_iconTop GitHub Comments

9reactions
newVincentFongcommented, Jan 16, 2020

Environment

  • .NET Core SDK 3.1
  • VSCode C# Extension 1.21.9
  • Mac

Reference

OmniSharp/omnisharp-vscode Wiki

If you had Visual Studio Code open at the time you installed the .NET SDK, and you haven't restarted it, you should do so.

My Solution

Exit VSCode and open it…

Reason

I try not to exit vscode on my mac when it’s connected to a monitor because vscode has some GPU rendering problem in this circumstances. This habbit leads to the problems.

7reactions
Cabolacommented, Jun 2, 2020

If there’s still people having this issue then try this:

  1. From start menu search for “this pc”, right click and select properties.
  2. Click Advanced system settings
  3. Click on “Environment Variables…”
  4. Select either the Users or Systems “Path” variable and click Edit…
  5. In either of them you should find the path to your “dotnet” folder

now in my case I had 2 C:\Program Files (x86)\dotnet\ and C:\Program Files\dotnet\ if you actually go to the folders you’ll notice that there’s no sdk folder within the C:\Program Files (x86)\dotnet\ folder. So simply select C:\Program Files\dotnet\ and click the “move up” button. Then click OK all the way out of there, now try and see if things are working…

Read more comments on GitHub >

github_iconTop Results From Across the Web

The .NET Core SDK cannot be located. .NET Core debugging ...
The .NET Core SDK cannot be located. .NET Core debugging will not be enabled. Make sure the .NET Core SDK is installed and...
Read more >
Troubleshooting: 'The .NET Core SDK cannot be located.' errors
Bring up System Properties: · Go to the Advanced settings · Click the button for 'Environment Variables' · Find 'Path' in either the...
Read more >
Visual Studio Code Error: The .Net Core cannot be located - Ask
NET Core SDK cannot be located. .NET Core debugging will not be enabled. Make sure the .NET Core SDK is installed and is...
Read more >
Error during C# set up on Visual Studio: The .NET Core SDK ...
Error during C# set up on Visual Studio: The .NET Core SDK cannot be located. .NET Core debugging will not be enabled. Make...
Read more >
Unable to locate the .NET SDK: The Reasons - Hamid Mosalla
Navigate to C:\Program Files\dotnet\sdk and see if you can find folders associated with different sdk versions. If you can't find any folder ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found