.editorconfig doesn't support dotnet_diagnostic in Rider

Avatar
Drew Forsberg
Created

Hi,

My team and I recently switched from using VS 2022 on Windows to using Rider (2025.1.4) on Mac (Sequoia 15.5). We had customized our .editorconfig files to enforce various dotnet_diagnostic warnings (null references, unused variables, etc) as errors that need to be addressed before building and merging. I've noticed that Rider does not enforce those policies and oddly, looking at them in .editorconfig, Rider doesn't even appear to support them, even though your documents say “dotnet_diagnostic.* — supported for all compiler warnings.”

Note that line 106 includes an entry that I copied directly from your website.

Can you please help?

Thanks,

Drew

Votes

4

Share

2 comments
Avatar
Drew Forsberg
Created

Tom Luo Kirill Filin @...  or other JetBrains folks--could you please respond to my post? My team and I have been patiently waiting for over a month. Thanks.

0
Avatar
Tom Luo
Created

Hello Drew,

Sorry for the late response. This ticket was misrouted somehow and not on our radar. 

Regarding this issue, I have tried this rule in my environment and it’s functioning as expected.

Note, we have a known issue that Roslyn rule properties are not recognized in editorconfig: Support roslyn properties in editorconfig : RIDER-51400. However, this only impacts the frontend UI visibility—the rules themselves are fully supported and should work correctly.

If you’re still encountering issues, could you please create a demo project along with .editorconfig file demonstrating the issue? You can upload it to the Upload Service and share the Upload ID.

This will help us investigate further. Let me know if you have any questions.

Thanks,

Tom

0

Please sign in to leave a comment.