Update AnalyzerReleases shipped file for 7.0 release

[mavasani]

Fixes #6245

I verified that locally built NuGet package with this fix resolves this issue. The NuGet package contains analysislevel_7_XXX.editorconfig set of editorconfig files, and setting AnalysisLevel to latest-XXX or latest or 7.0 passes in the appropriate editorconfig file to compiler command line

Filed #6247 to enhance the tooling to avoid regressions such as #6245 in future.

[mavasani]

@Evangelink @jmarolf for review

[codecov]

Codecov Report

Merging #6246 (de1013f) into main (55d7cdc) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6246   +/-   ##
=======================================
  Coverage   96.04%   96.04%           
=======================================
  Files        1360     1360           
  Lines      312054   312054           
  Branches    10047    10047           
=======================================
+ Hits       299720   299724    +4     
+ Misses       9925     9924    -1     
+ Partials     2409     2406    -3     

[mavasani]

@jmarolf can we do an insertion of the latest NetAnalyzers package into dotnet/sdk after this change?

[jmarolf]

let me verify that is happening

[znakeeye]

Just installed Visual Studio 17.4.0 and re-compiled my project. Still no CAxxxx warnings produced when targeting net7.0. Is this expected?

[mavasani]

@znakeeye The fix still needs to flow from this repo to dotnet/sdk repo and make it into the next .NET 7 servicing release. Additionally, VS also needs to move to the newer .NET 7 release with the fix for it to automatically light up. This whole code flow and release process can take some time, so meanwhile I would suggest you to directly install the latest prerelease NuGet package from this feed instead: https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet7/NuGet/Microsoft.CodeAnalysis.NetAnalyzers

Note that you should avoid setting EnableNETAnalyzers MSBuild property to true in your project file/props/targets, as that would in turn override the installed NuGet package analyzers with the old ones shipping inside the .NET SDK (which don't yet have this fix).

[znakeeye]

@znakeeye The fix still needs to flow from this repo to dotnet/sdk repo and make it into the next .NET 7 servicing release. Additionally, VS also needs to move to the newer .NET 7 release with the fix for it to automatically light up. This whole code flow and release process can take some time, so meanwhile I would suggest you to directly install the latest prerelease NuGet package from this feed instead: https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet7/NuGet/Microsoft.CodeAnalysis.NetAnalyzers

Note that you should avoid setting EnableNETAnalyzers MSBuild property to true in your project file/props/targets, as that would in turn override the installed NuGet package analyzers with the old ones shipping inside the .NET SDK (which don't yet have this fix).

Ok, so in order to get it to work with .NET 7 you should:

1. Install VS 17.4
2. Comment out EnableNETAnalyzers
3. Install latest prelease of Microsoft.CodeAnalysis.NetAnalyzers

Correct? Or do we need 17.5p1? (I saw it was referenced here, somewhere...)

[jmarolf]

@mavasani I can confirm this made it into the .NET SDK here: dotnet/sdk#28864. It should be part of the first servicing release.

[mavasani]

Thank you @jmarolf

[znakeeye]

I suppose this was fixed in SDK 7.0.101 then?

[mavasani]

I suppose this was fixed in SDK 7.0.101 then?

Yes, correct.