Rider was unable to detect MSBuild

[kostat]

18/10/2021
12:09 Rider was unable to detect MSBuild
If you think this is an error, please specify a path to MSBuild in Rider settings.
Alternatively, to develop .NET applications, install install .NET Core or Mono.

---

This is where the files are located when running Rider installed with snap:

The flatpak sandbox does not have access there

[ZagButNoZig]

Rider has the host filesystem sandbox permission. This permission allows it to access the whole file system except some blacklisted ones, which also includes /usr where dotnet is located but /usris mounted under /var/run/host/usr. So in order to solve this problem you need to set the executable path to /var/run/host/usr/share/dotnet.

[mfilippov]

I added support .net and mono detection in /var/run/host. It will available in Rider 2022.1.

[DFSko]

In Fedora dotnet located in /usr/lib64/dotnet
After adding /var/run/host/usr/lib64/dotnet to .Net CLI executable path SDK and MSBuild found but i have this error:

MSBuild process was started from '/var/run/host/lib64/dotnet/sdk/6.0.105/MSBuild.dll', but IDE failed to connect to it. It means MSBuild crashed or froze during startup.

[mfilippov]

Thanks for the update. I will take a look on .NET SDK detection.

[Frankwayne]

I'm on WSL2 and I don't have a

/var/run/host

folder. I'm trying to set up remote development on WSL2.

[Frankwayne]

apparently the dotnet-runtime does not get installed with the aspnet core runtime

dotnet/sdk#38794 (comment)