Rider was unable to detect MSBuild

flathub / com.jetbrains.Rider

https://flathub.org/apps/details/com.jetbrains.Rider

2 stars 7 forks source link

Rider was unable to detect MSBuild #36

Open kostat opened 2 years ago

kostat commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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

DFSko commented 2 years ago

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 commented 2 years ago

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