Struggling to programmatically retrieve some IDE diagnostics with severity=suggestion starting with .NET 9.0.2

[tdg5]

Hello! I apologize for the open-ended question, but I've spent a few hours on this problem and feel no closer to a solution.

TL;DR - Does anyone know why I might not be able to programmatically retrieve IDE**** diagnostics with severity=suggestion starting with .NET 9.0.2?

I have a project that includes a test suite to ensure that editor rules are enforced as expected. Previously I was able to gather IDE**** diagnostics using this code:

    public IEnumerable<Diagnostic> AnalyzeProject(string projectPath)
    {
        var project = workspace.OpenProjectAsync(projectPath).Result;
        var analyzers = project
            .AnalyzerReferences
            .SelectMany(r => r.GetAnalyzers(project.Language))
            .ToImmutableArray();
        var compilation = project.GetCompilationAsync().Result
            ?? throw new InvalidOperationException("Failed to compile project.");

        var compilationWithAnalyzers = compilation.WithAnalyzers(analyzers);

        var diagnostics = compilationWithAnalyzers.GetAnalyzerDiagnosticsAsync().Result;

        return diagnostics;
    }
}

But now I don't seem to be able to do so. To be clear, I've made no code changes since this worked. I thought maybe I was filtering them out over here, but I tried writing all the diagnostics to console and none of them are IDE diagnostics.

The specific suggestion severity diagnostics I am unable to detect are:

IDE0028 (implicitly has severity suggestion)
IDE0039
IDE0042
IDE0045
IDE0046
IDE0048
IDE0056
IDE0057
IDE0066
IDE0070
IDE0072
IDE0078
IDE0120
IDE0180
IDE0230
IDE0250
IDE0251
IDE0260
IDE1006

It's worth noting that I also have CA1001 configured with a severity of suggestion, and that one continues to work fine. So I'm not sure if this is an IDE**** thing or a severity=suggestion thing or some combination of the two.

Thanks in advance for any and all help!

[JoeRobich]

@tdg5 Maybe a good place to start is to log out which AnalyzerReferences are added to your project.

[tdg5]

Thanks for the suggestion @JoeRobich. I'm able to confirm that the IDE diagnostics could be discovered with AnalyzerReferences in .NET 9.0.10{0,2,3} (example debug output), but they are no longer discoverable in .NET 9.0.200 (example debug output).

More specifically, it seems like they were made visible by the package versions listed below but are no longer visible with Microsoft.CodeAnalysis.CSharp.CodeStyle, Version=4.13.12.7211, regardless of configured severity.

• Microsoft.CodeAnalysis.CSharp.CodeStyle, Version=4.12.11.2304 (.NET 9.0.100) [ build ]
• Microsoft.CodeAnalysis.CSharp.CodeStyle, Version=4.12.11.7408 (.NET 9.0.102) [ build ]
• Microsoft.CodeAnalysis.CSharp.CodeStyle, Version=4.12.11.13101 (.NET 9.0.103) [ build ]

It also seems like the IDE diagnostics from Microsoft.CodeAnalysis.CodeStyle follow the same pattern.

Any thoughts on where to go from here? This info seems like it should narrow down the source of the discrepancy, but I don't know how to translate these versions into further digging.

This comparison might offer some info, but there's a lot to go through: NET-SDK-9.0.103...NET-SDK-9.0.200

Similarly, something like git diff NET-SDK-9.0.103 NET-SDK-9.0.200 could be helpful, but is again pretty overwhelming.

A question I'm asking to try to get somewhere with this problem is "What would cause AnalyzerReference.GetAnalyzers to change behavior?".

I don't have any real reason to blame it, but this commit, Reapply "Load analyzers and generators in isolated ALCs in our OOP process", isn't in any of the 9.0.10x trees, but is in the 9.0.200 tree. It could certainly impact the analyzers returned by a Workspace. Maybe I've configured something wrong and was previously getting non-isolated access to the IDE analyzers?

I'm out of juice for this right now 😓 .

Any ideas or direction are welcome! Thanks again, any and all!

[tdg5]

A potentially related question I might ask, but don't see any particular guidance for is... Is there something special I have to do to use the Nuget version of Microsoft.CodeAnalysis.CSharp.CodeStyle instead of the SDK version? I'm a little surprised that each build shows a different version of Microsoft.CodeAnalysis.CSharp.CodeStyle when in my .csproj file I have

<PackageReference Include="Microsoft.CodeAnalysis.CSharp.CodeStyle" Version="4.11.0"/>

I thought maybe something was forcing that package to <PrivateAssets>all</PrivateAssets>, so I tried adding to tests via Directory.Build.props, but that didn't seem to make a difference.

I guess it's worth stating for clarity that I want Microsoft.CodeAnalysis.CSharp.CodeStyle to be a dependency for projects that install the Tdg5.StandardConventions package. Tdg5.StandardConventions should then be used with <PrivateAssets>all</PrivateAssets>.