[BUG] .NET not found in PATH, but exists in my computer even I install the .NET SDK and set the PATH variable in VSCode

[lulunac27a]

Describe the Issue

When I installed the latest version of .NET SDK, VSCode shows that .NET SDK is not installed, but .NET SDK was already installed and the executable is already in the PATH environment variable.

Steps To Reproduce

1. Install the latest version of .NET SDK.
2. Add the path of .NET SDK executable in PATH variable.
3. Open VSCode and reload windows.
4. See the error message on buttom right of the window.

Expected Behavior

Successfully lint and show autocompletion features without showing an error message.

Environment Information

• OS: macOS 15.0
• VSCode Version: v1.95.2
• Extension Version: C# Dev Kit v1.13.9

[lulunac27a]

I use code . command and C# language server initialized successfully, but linting and autocompletion were not loaded successfully.

[lulunac27a]

C# Dev Kit logs:

Failed to listen to project initialization status: Error: Activating the "Microsoft.VisualStudio.ProjectSystem.ProjectInitializationStatusService (0.1)" service failed.
Failed to subscribe to active projects: Error: Activating the "Microsoft.VisualStudio.ProjectSystem.Query.Remoting.QueryExecutionService (0.3)" service failed.

[lulunac27a]

I found the .NET runtime version in VSCode log: Using local .NET runtime at "/Users/lulu/Library/Application Support/Code/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/8.0.11~arm64~aspnetcore/dotnet". How can I update the runtime version to the latest version (v9.0) so VSCode matches that version because I already installed the latest version of .NET in my computer?

[lulunac27a]

Still not working when I set omnisharp.sdkPath (Omnisharp: Sdk Path) to installed executable of /usr/local/share/dotnet, /usr/local/share/dotnet/dotnet or /opt/homebrew/bin/dotnet.

[lulunac27a]

Even when I create the profile in VSCode, the linting and auto code completion features still doesn't work.

[arunchndr]

@nagilson would you please scout this one and reroute?

[nagilson]

The .NET runtime thats resolved as 8.0 is for the C# extension to run its code under, so it doesnt need to be 9.0. That extension is written in 8.0 right now.

The problem is that the SDK is not being found correctly likely by C# DevKit. We wrote an API to find the SDK better for DevKit, which @adrianvmsft is working on using which should fix this issue.

@lulunac27a For a workaround for now -- can you try to -- launch vscode from the terminal? If you launch from the dock in mac sometimes vscode doesn't get the environment correctly. You can also try to set DOTNET_ROOT to your dotnet executable path and then launch from the terminal and see if it works.

[lulunac27a]

The linting and autocompletion suggestions are still not working when I set DOTNET_ROOT to /usr/local/share/dotnet and the same when I open VSCode from the terminal using code .

[nagilson]

Thank you, that sounds like a bug with those areas, then. @lifengl May you please see why the linting and autocomplete is not working here? Or do you know a contact who works on the project system that would understand this better (@tmeschter?) @arunchndr, if you also have a project system contact that'd be helpful.

Sorry it is not working for you. As an alternative temporary solution (not sure if this will work), you might be able to install the SDK in a different way (mac installer on the website, via vscode walkthrough ui, homebrew, etc) but I doubt that's it.

[Dinesh41]

I too faced same issue in MAC, In my case already i had PATH variable setup done for dotnet using .zshrc file. However for some reason when we open VS directly, it uses some other terminal and taking wrong path like /usr/bin etc.
As a workaround, if we open terminal for the project and if we use code . , that solves the issue

[webreidi]

@nagilson / @JakeRadMSFT any update on this one? Does it need to be moved to the next milestone? Will switching to use the new API fix this?

[nagilson]

Please see #1565 (comment)

[nagilson]

The latest pre-release version of C# Dev Kit extension (1.16.4) has a new implementation for locating dotnet which should fix this.

To do that, you need to uncheck this setting located under Extensions -> C# -> C# Dev Kit: Dotnet: Use Legacy Dotnet Resolution.