.NET SDK10 Roslyn Analyzer Diagnostics `IDE0130` likely buggy

Question

Question

Answer 1

Danny Nguyen (WICLOUD CORPORATION) 8,015 Microsoft External Staff Moderator

Thank you for reporting this. I was able to reproduce this behavior locally. It appears to be a known limitation of the analyzer's current design rather than a bug.

The IDE0130 analyzer skips checking partial classes if they are spread across multiple files. This is because the automatic "fixer" tool (which runs when you try to automatically fix the warning in your editor) does not currently support fixing partial classes with multiple parts.

Because the tool cannot safely fix the warning for a partial class spread across a normal .cs file and a generated .g.cs file, it chooses to skip checking the rule completely to avoid showing a warning that it cannot automatically solve.

There is an open issue on the dotnet/roslyn repository tracking this exact limitation. A Microsoft team member confirmed this is currently the intended behavior, but they are open to fixing it based on community feedback.

You can view the issue here: IDE0130 does not report on partial classes (#72749).

I suggest upvoting that issue and leaving a brief comment about your experience with generated files. This helps the team understand how this limitation affects developers and may help prioritize a fix.

If this answers your question, I would greatly appreciate it if you could follow this guidance or provide feedback.

Thank you.

bic 25 Reputation points

2026-08-06T10:34:29.19+00:00
Thank you very much for your quick response and for pointing me in the right direction.

What I did after receiving your response:

read dotnet/roslyn issue you linked

upvoted

added a detailed explanation why I believe the current design could be improved

Since the issue has been open for about two years, I assume it may not be addressed in the near future. Is there anything I can do to help move it forward?

My alternative is writing a custom analyzer. While this is definitely an option, I think improving the design of IDE0130 would benefit the wider .NET community as well.
Danny Nguyen (WICLOUD CORPORATION) 8,015 Reputation points Microsoft External Staff Moderator

2026-08-06T11:04:06.8066667+00:00

Hi @bic ,

Thanks for taking the time to read the issue and add your reasoning — that's genuinely the most useful thing you could have done here, and it's the kind of feedback the team said they left the issue open to collect.

I'd stay with #72749 rather than opening a new one. A duplicate would just get closed and linked back, and it splits the feedback. The issue is already tracked under the Sync Namespace parent item, so it's on the team's list.

If you want to push it further, the fastest path is a PR. The behavior comes from one early-return check in AbstractMatchFolderAndNamespaceDiagnosticAnalyzer.cs for partial types with multiple declarations, and your point — report the diagnostic, just don't offer the fix when it isn't safe — is essentially the change that would be needed. Roslyn takes community PRs.

The custom analyzer is a fair interim option if this is blocking you now. It doesn't rule out the upstream fix, and you can drop it later.
bic 25 Reputation points

2026-08-06T15:16:18.64+00:00
Thanks again. I think at this point I will follow the steps just as you suggested:

create interim custom implementation

(link custom implementation here if that's ok)

experiment with AbstractMatchFolderAndNamespaceDiagnosticAnalyzer.cs

create PR accordingly when ready

.NET SDK10 Roslyn Analyzer Diagnostics `IDE0130` likely buggy

Description

Issue

Expected Behavior?

Question

0 additional answers

Your answer