dotnet executable file not found in $PATH when installed through Jetbrains Rider

[cfgiugliano]

Describe the bug

I've installed Jetbrains Rider on macOS and it asked to take care of installing .NET SDK so I accepted. Once completed, Rider was able to build and run .NET projects but dotnet --info from terminal didn't return anything. Furthermore running an Aspire project ran all the projects except the dashboard:

failed to start a process {"Executable": {"name":"aspire-dashboard-hfyxpzxx"}, "Reconciliation": 5, "error": "exec: "dotnet": executable file not found in $PATH"} 

The executable was installed under /Users/example/.dotnet/

I've tried using dotnet-core-uninstall to remove it but both SDK and runtime weren't detected.

Manually deleting the directory and installing .NET using the package downloaded from dotnet website fixed it.

Further technical details

• MacBook Pro M4 with macOS 15.4
• JetBrains Rider 2024.3.7
• SDK 9.0.200 (or 9.0.202, I'm not sure which was installed by Rider)
• dotnet-core-uninstall 1.7.618124+6f834e098fd32238e670f2d52c58745cf4e39054

[baronfel]

Can you dump the contents of the integrated terminal in Rider after it installs the SDK? I'm especially interested in PATH and DOTNET_ROOT (if present) - those two are the main load-bearing variables.

If PATH/DOTNET_ROOT are changed/updated by Rider during a single Rider session, it's possible that it might be changing your shell profile correctly, but that you need to start a new terminal session to pick up those changes. That's a relatively common requirement.

[cfgiugliano]

It doesn't seem to output anything, It runs a background task which install .NET but I can't see any content in the terminal. I think they aren't set as even restarting Rider or the system doesn't change anything.

[nagilson]

What is included in your PATH environment variable with just rider installed? Same for DOTNET_ROOT? What files did it dump into /Users/example/.dotnet/? It seems this is an issue with how rider is installing the SDK, so I would reach out to them as well to fix this bug.