Rider update broke loading and building projets

Hi! 
You can download an older version of Rider or downgrade via Toolbox.

However, to analyze the case, I'd like to ask for some more details. What kind of project do you have? What is the exact error message appears, if any? Have you tried the Reload project option? 

Also, it would help if you could collect and share logs: SUPPORT-A-275 How to collect Rider logs with Traces. You need to choose a ProjectModel scenario and reopen\build your solution.  

Thanks! 

Edit: Nevermind, I went back to 2024 Rider and it still didn't work. Will submit a ticket

I was on my way to submit a support ticket but saw this come up, so I'll make a comment here too

I'm on Linux with Bazzite and kept having issues with references with my work project, which had previously been working fine on NixOS

Installed JetBrains toolbox with official installer

So to replicate the issue, I setup a new solution that contained a Console project, Library project (called Common which is referenced by Console project), and xUnit test library, which references the Console.

When I build the unit test I get the following error:

`Microsoft.Common.CurrentVersion.targets(1815, 5): [MSB3202] The project file "../../../../../../var/home/myUser/RiderProjects/JetBrainsTest/JetBrainsTest.Common/JetBrainsTest.Common.csproj" was not found.`

I enable/disable “JetBrains Build” in the Rider build options but it still breaks

I go into my Terminal and run “dotnet build” and “dotnet test” and it works perfectly

Hi, thank you for answers.
When I start Rider (loading a sln or project) or when I build, I get the following error:
"MSBuild process was started from '/Users/pierre/.dotnet/sdk/9.0.200/MSBuild.dll', but the IDE failed to connect to it.
It means that MSBuild crashed or froze during startup."
I didn't install .Net 9.
I can build and run using the dotnet CLI command.
 

Hi Ptheate! 

Thanks! 
Please attach the following information: 

• screenshot of File | Settings | Environment
• screenshot of File | Settings | Build, Execution, Deployment | Toolset and Build
• output of dotnet --info 
• please try to create a sample console app. Does it work? 

Hi Andrew James Bowen! 
As I can see, you have a different problem and already discussed it with my colleague. 

Hi,

It seems you didn't notice I am using a MacBook (Settings are not in File menu) but here are the screen shots.

As I mentioned, it is trying to use .Net 9 that I didn't install.

In MSBuild version dropdown. there is only 1 entry, again for .Net 9 sdk.

Here is dotnet --info output:
SDK .NET :
Version:           8.0.410
Commit:            0c2bff86e8
Workload version:  8.0.400-manifests.def3829e
MSBuild version:   17.11.31+933b72e36

Environnement d'exécution :
OS Name:     Mac OS X
OS Version:  11.7
OS Platform: Darwin
RID:         osx-x64
Base Path:   /usr/local/share/dotnet/sdk/8.0.410/

Charges de travail .NET installées :
Configuré pour utiliser loose manifests lors de l’installation de nouveaux manifestes.
Il n'y a aucune charge de travail installée à afficher.

Host:
 Version:      8.0.16
 Architecture: x64
 Commit:       efd5742bb5

.NET SDKs installed:
 8.0.410 [/usr/local/share/dotnet/sdk]

.NET runtimes installed:
 Microsoft.AspNetCore.App 8.0.16 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
 Microsoft.NETCore.App 6.0.36 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
 Microsoft.NETCore.App 8.0.16 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
 None

Environment variables:
 Not set

global.json file:
 Not found

Learn more:
 https://aka.ms/dotnet/info

Download .NET:
 https://aka.ms/dotnet/download
 

Ptheate thanks! 
As I can see, Rider tries to find .net by the following path: "/Users/pierre/.dotnet/sdk/9.0.200/". However, your sdk is installed to /usr/local/share/dotnet/sdk. 

So, could you please specify the /usr/local/share/dotnet/sdk path to .NET CLI executable path setting and check if it helps? 

Thank you for your quick answer.

Yes, it helps, everything adapted to the installed .Net 8 SDK and now it works.

Thank you.