Rider stuck on "Toolset and Build" loading
I'm trying to connect Rider to WSL.
First problem that Riders seems to be unable to resolve dotnet version managed by asdf, but when I try to specify path in settings, it is getting stuck forever in that “loading” screen when trying to open “Toolset and build”.
Running application from terminal - “dotnet watch” works.
But truying to run it by Rider gives following error -
You must install .NET to run this application.
App: /home/ilyus/projects/...
Architecture: x64
App host version: 6.0.26
.NET location: Not found
Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed
Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=ubuntu.22.04-x64&apphost_version=6.0.26
Process finished with exit code 131.
Please sign in to leave a comment.
There could be some compatibility problems with the dotnet SDK managed by asdf. Please refer to this answer in the existing thread.
Basically, dotnet allows to install multiple SDK versions on a same machine, and usually it's specified in global.json.
For the settings keep loading issue in the screenshot, it's a known issue in the EAP version.
RIDER-105384 rider remote development cannot fix issue in settings
We would appreciate it if you would upvote it and click
Watchto monitor the status.thank you for the reply!
I'm following the issue now.
When settings will work I will check does it allow me to specify path to dotnet managed by asdf there.
I have .tool-versions file to manage dotnet version, but I ofc ca cnreate global.json if it will help rider somehow
I am using Ubuntu 24.04 and had the same issue.
According to what I found, there is probably a very simple solution to this issue. I have spent hours trying to find out why I got this “.NET location: Not found” message. I tried both snap and .tar.gz versions of Rider as well as both apt and .tar.gz versions of dotnet and dotnet sdks with absolutely no success. Then I tried choosing “custom” runtime with “/usr/lib/dotnet/dotnet” (which is the apt install location) and suddenly it worked like a charm. I only figured this out after many hours of searching the web where finally I read a comment that dotnet should be in the path and then Rider will find it. Actually, this is only half true. In Linux (Ubuntu) dotnet will be available in the path after an install via a package manager, but it will be without adding a folder to the path. The following command will get the real installation path that works:
On my Ubuntu machine, the above statement resolves to “/usr/lib/dotnet/dotnet”, which works as a “custom” runtime. So what needs to happen is that Rider must resolve the real path where dotnet is located.
John Bester Did you add the required environment variables when running apt installation for dotnet SDK? Rider will try to find the PATH declaration first.
Of course, you can specify the toolset path manually as well.
Seeing that there is a snap install which I used, I did not think there should be any manual instructions needed before doing `snap install`. The `--classic' option that is required is reported if you do not use it. The solution I mentioned is simple to implement and would not required additional manual steps for installation.
Rider will refer to using DOTNET_ROOT to locate the actual SDK installation path, you will have to add the environment after installation. It will not be configured by snap automatically.