.NET 6 Code analyzer CodeAnalysisTreatWarningsAsErrors breaking - visual-studio

Question

We are trying to enable to .NET 6 Code Analyzer on our .NET 472 projects.
In most projects we have WarningsAsErrors set to true. We dont want to CA warnings to report as an error, so we added CodeAnalysisTreatWarningsAsErrors as false.
When doing so, all the CA warnings are no longer reported
We now use the following settings
<PropertyGroup>
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>latest-recommended</AnalysisLevel>
<CodeAnalysisTreatWarningsAsErrors>false</CodeAnalysisTreatWarningsAsErrors>
<WarningsNotAsErrors>$(WarningsNotAsErrors);CS8073;CS8882;CS8887;CS8848</WarningsNotAsErrors>
</PropertyGroup>
Without the settings, we have 0 warnings. With these settings, only a few additional CS warnings are triggered, the ones we had to add in the WarningsNotAsErrors
If i remove the CodeAnalysisTreatWarningsAsErrors property and set TreatWarningsAsErrors to false, i get 1700 CA warnings in our code base.
I would expect to see these 1700 warnings with above settings as well.
When i set CodeAnalysisTreatWarningsAsErrors to true, i get 1700 errors.
I am using this in my global.json file
{
"sdk": {
"version": "6.0.300",
"rollForward": "latestFeature"
}
}
and have sdk's 6.0.300 and 6.0.401 installed, along with VS 17.2
Why is CodeAnalysisTreatWarningsAsErrors breaking our code analysis scan?
Any advice would be helpful.
Edit: adding images
VS shows it wants to treat them as warning:

Answer 1

I set TreatWarningsAsErrors and CodeAnalysisTreatWarningsAsErrors to true or false for Combinatorial testing. Below are several test results.
scenario 1
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
This returns all CS errors.
scenario 2
<TreatWarningsAsErrors>false </TreatWarningsAsErrors>
This returns all CS warnings.
scenario 3
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>latest-recommended</AnalysisLevel>
scenario 4
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>latest-recommended</AnalysisLevel>
<CodeAnalysisTreatWarningsAsErrors>true</CodeAnalysisTreatWarningsAsErrors>
Both 3 and 4 returns CS and CA errors.
scenario 5
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>latest-recommended</AnalysisLevel>
<CodeAnalysisTreatWarningsAsErrors>false </CodeAnalysisTreatWarningsAsErrors>
This returns CS errors and CA warnings.
scenario 6
<TreatWarningsAsErrors>false </TreatWarningsAsErrors>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>latest-recommended</AnalysisLevel>
<CodeAnalysisTreatWarningsAsErrors>false</CodeAnalysisTreatWarningsAsErrors> (Or it can be removed)
This returns CA and CS warnings.
From your description,
I would expect to see these 1700 warnings with above settings as well.
My understanding is that if you want to see warnings, you can follow scenario 6. I’m afraid you can’t see these 1700 warnings with above settings as well.
<TreatWarningsAsErrors>true</TreatWarningsAsErrors> <CodeAnalysisTreatWarningsAsErrors>false</CodeAnalysisTreatWarningsAsErrors>)
But I'm not sure exactly what your question is from your last paragraph.
If there is any misunderstanding, please feel free to let me know.
UPDATE1/30/2023
If scenario 5 doesn't work in your machine, i suggest you check below setting 1 and setting 2 or try method 3.
1 Custom analysis scope
By default, compiler diagnostics run on all open documents, and, in Visual Studio 2022 and later, Roslyn analyzer diagnostics run on the currently active document only.You can custom analysis scope.For example:
2 set warning levels
3 Run code analysis manually
Error list will soon refresh with all code analysis diagnostics.Please refer to doc: Run code analysis manually
UPDATE 2/2/2013
Steps below are my process of creating demo project and getting the warnings. You can follow those steps and see if warnings are show.
1 create C# console app project named CodeAnalyzeTest.
2 copy code below to Program.cs and install package Newtonsoft.Json
using Newtonsoft.Json;
namespace CodeAnalyzeTest
{
public class Account
{
public string Name { get; set; }
public string Email { get; set; }
public DateTime DOB { get; set; }
}
public class Program
{
static void Main(string[] args)
{
Account account = new Account
{
Name = "John Doe",
Email = "john#nuget.org",
DOB = new DateTime(1980, 12, 20, 0, 0, 0, DateTimeKind.Utc)
};
string json = JsonConvert.SerializeObject(account, Formatting.Indented);
Console.WriteLine(json);
}
}
}
3 edit project file and add PropertyGroup
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net6.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
<PropertyGroup>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>latest-recommended</AnalysisLevel>
<TreatWarningsAsErrors>false</TreatWarningsAsErrors>
<CodeAnalysisTreatWarningsAsErrors>false</CodeAnalysisTreatWarningsAsErrors>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Newtonsoft.Json" Version="13.0.2" />
</ItemGroup>
</Project>
4 build the project and watch error list.You'll get CA and CS warnings.
If you still get no warnings after following steps above, please provide Minimal, Reproducible Example that we can easily understand and use to reproduce the problem.