AnalysisLevel latest not using the correct set of rules

[bording]

Describe the bug

When setting AnalysisLevel to latest in a project, the 9.0 rules are being chosen instead of the 10.0 rules.

I believe the cause for this is that the _LatestAnalysisLevel property in Microsoft.NET.Sdk.Analyzers.targets was not incremented for the .NET 10 SDK.

_PreviewAnalysisLevel also looks to be incorrect.

I can see that there are tests related to checking these properties, but based on the comments I can see on those tests, it looks like they weren't updated either.

To Reproduce

1. Create a new console app targeting net10.0
2. Add <AnalysisLevel>latest</AnalysisLevel> to the project file
3. Build the project and create a binlog (dotnet build -bl)
4. In the binlog, you can see that the _GlobalAnalyzerConfigFileName_MicrosoftCodeAnalysisNetAnalyzers property value is analysislevel_9_default.globalconfig instead of analysislevel_10_default.globalconfig

Exceptions (if any)

N/A

Further technical details

details of dotnet --info

.NET SDK: Version: 10.0.102 Commit: 4452502459 Workload version: 10.0.100-manifests.6d969a7e MSBuild version: 18.0.7+445250245

Runtime Environment:
OS Name: Windows
OS Version: 10.0.26200
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\10.0.102\

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.

Host:
Version: 10.0.2
Architecture: x64
Commit: 4452502459

.NET SDKs installed:
9.0.306 [C:\Program Files\dotnet\sdk]
10.0.102 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 10.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 10.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 8.0.21 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.23 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 10.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

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

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

- The IDE (VS / VS Code/ VS4Mac) you're running on, and its version: Microsoft Visual Studio Professional January 2026 Feature Update 18.2.0

[baronfel]

Good analysis (heh).

Well want to fix it and backport it to 100 and 200 servicing releases.

[bording]

@baronfel While digging into this and looking through the relevant targets files, I realized that the AnalysisLevel documentation doesn't seem to align with how it actually works. The docs say that latest is the default, but since _TargetFrameworkVersionWithoutV is being using when AnalysisLevel is unset, that results in a rules version matching the TFM being chosen.

This means that when you have a multi-targeted project, each TFM uses a different set of rules. Since the docs say latest is the default, I would have expected a single version being chosen for all TFMs and it being tied to the latest version of the rules in the SDK.

What do you think of this mismatch? Should I open another bug issue for it?