Unable to build projects due to references in Bazzite

Hello Andrew, 

Thanks for contacting Rider support. Regarding this issue, could you try the following to help us isolate the issue:

• Go to Rider Settings | Build, Execution, Deployment | Toolset and Build, then confirm “MSBuild version” is set to the same one you used for “dotnet build”:

• We are aware of a similar issue that is caused by symbolic linked directory usage. Would you mind verifying if you use symbolic links? I also recommend trying to clone the project you shared into home directory and trying to open the newly cloned solution from Rider to see if that helps.

Please let me know if the issue persists. 

Thanks,

Tom

I'm encountering exactly the same problem also under Bazzite. I've got only one dotnet SDK installed and that is 9.0.304 [/var/home/bazzite/.dotnet/sdk] which got installed by Rider itself.

Hello Oliver, 

Could you confirm if you're using symbolic linked directory in the project? If yes, could you try to move the project to home directory and open it from there? 

Let me know if this does not match your scenario. I will then investigate further. 

Thanks,

Tom

Clean repo freshly cloned using Github CLI. No symbolic links. Freshly installed system.

Any update on this?

Hello Oliver, 

Thanks for the additional details. In this case, I would suggest the following:

1. Go to Settings | Build, Execution, Deployment | Toolset and Build, then uncheck “Use ReShaper Build” as below:

This option disable the build optimizaiton in Rider, and shoud revert to the default behavior of msbuild. 

2. If the issue continues, for better tracking, please report this issue on our bug tracker with following details:
a) The full log bundle. You can collect it via Help | Collect Logs and Diagnostic Data;

b) Complete console output that contains error message. 
 

The ticket will be handled by a dedicated developer there. You can upvote it to indicate your interest and subscribe to further status updates.

Thanks,

Tom

Disabling Use Resharper Build has zero effect. Andrew already tried that above. Quite disappointing. Bug Tracker tickets often take years to resolve. 

Hello Oliver, 

I completely understand your frustration—no one likes waiting for fixes, especially when delays happen. While some issues indeed take a long time to resolve due to complexity or lack of resources, many are addressed much faster. Proper reporting ensures the issue gets the attention it deserves.

By logging the issue, you’ll help us track and prioritize it more effectively. I'm glad to bring this to the attention of our developer team and request them to prioritize it. Could you share the ticket link once it’s created? I’ll make sure it’s on their radar. 

Regards,

Tom

OK, I know this is an old thread, but its a top search result for JetBrains Rider Bazzite, and I have found something useful.

I too was getting the error: 

Microsoft.Common.CurrentVersion.targets(1815, 5): [MSB3202] The project file ”blah blah blah.csproj" was not found.

I came across this issue for Bazzite-dx: https://github.com/ublue-os/bazzite-dx/issues/127#issuecomment-3263772604

opening rider by using the console rider ./path/to/mysolution.sln caused Rider to startup and load the solution, and it was able to just build as I expected. I don't know why it makes a difference, but it does.

I wanted to share another workaround in this thread, since none of the suggested solutions worked on my system and I wasted a lot of time trying to find a fix.

- Open the list of your run configurations at the top (next to the Launch button), then click “Edit Configurations…” at the bottom.
- Scroll down to the “Before Launch” section.
- Remove the (single) entry that runs the build.
- Use the “+” button to add a new “Run External tool” entry.
- Enter the following information:
 Name: Build
 Program: dotnet
 Arguments: build
- Click “OK” and save.

This setting must be changed for each project — so it’s just a workaround!
If the “dotnet” program cannot be found, simply enter the full path to the executable from the settings under “Build, Execution, Deployment” (e.g., /usr/share/local/dotnet/dotnet).

I just ran into this issue as well. I tried the workaround mentioned 2 comments above and was able to open my solution.

OK, I know this is an old thread, but its a top search result for JetBrains Rider Bazzite, and I have found something useful.

I too was getting the error: 

Microsoft.Common.CurrentVersion.targets(1815, 5): [MSB3202] The project file ”blah blah blah.csproj" was not found.

I came across this issue for Bazzite-dx: https://github.com/ublue-os/bazzite-dx/issues/127#issuecomment-3263772604

opening rider by using the console rider ./path/to/mysolution.sln caused Rider to startup and load the solution, and it was able to just build as I expected. I don't know why it makes a difference, but it does.

Thank you all for continuously sharing the workaround. This will definitely help others facing similar issues. 

Since the issue disappears when launching Rider in the terminal, I suspect this might be related to environment variables loading - Rider typically loads environment variables configured in ~/.profile or ~/.bash_profile (login shell), but not in interactive shell configuration files (like, ~/.bashrc). If anyone can reproduce the issue, please try the following to further narrow down the issue:

1. Run “dotnet --info” to confirm dotnet installation information. 

2. Add PATH environment in ~/.profile or ~/.bash_profile to include dotnet path. Setting DOTNET_ROOT there may also help.

If the issue persists, please report this issue on our bug tracker with the following details:
a) The full log bundle. You can collect it via Help | Collect Logs and Diagnostic Data;

b) Complete console output that contains error message. 

c) Output of dotnet --info

This information will help us diagnose the root cause more effectively. Thanks for your cooperation!