The .NET CLI tools cannot be located
See original GitHub issueFrom @Tobyee on July 27, 2016 5:56
- VSCode Version: 1.3.1
- OS Version: Win7-x64
- dotnet Version: 1.0.0-beta-001598
Steps to Reproduce:
- cmd: mkdir demo & cd demo
- cmd: dotnet new
- cmd: dotnet restore
- cmd: code .
Error:
I’am sure that .NET Core SDK for Windows was installed and dotnet
command can be execute in cmd
.
See alse:
https://github.com/dotnet/cli/issues/3858
Copied from original issue: Microsoft/vscode#9831
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
VS Code error "The .NET CLI tools cannot be located..."
The executable was most likely installed in /usr/local/share/dotnet/dotnet . A symbolic link needs to be created to usr/local/bin for Visual Studio.
Read more >Troubleshoot .NET tool usage issues - Microsoft Learn
The .NET CLI tries to add the default location to the PATH environment variable on its first usage. However, there are some scenarios...
Read more >net CLI tools cannot be located. dotnet command does not run ...
For the dotnet command to work on the internal terminal in both cmd and powershell. Also for .net core debugging to be enabled...
Read more >VS Code: "The .NET CLI tools cannot be located." - Unity Forum
Hi, We just started using Unity and are using Visual Studio Code for code editing in Unity. Every time we open Visual Studio...
Read more >How to Fix The .NET Core SDK cannot be located ... - YouTube
Today we will fix the .NET Core missing problem of Visual Studio Code. It happened when we installed C# Extension on Visual Studio...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@gregg-miskelly Thanks for you tips. I found the reason. It’s because I have a old version cli tools installed that influence on the new one.
The old version install is: The new version install is:
I uninstall the old one then it fixed.
@EliasCK if you are running into a problem related to this and would like some help, or have a concrete suggestion, please open a new issue so we can help understand what is going on on your machine.