.NET 7.0 developers can verify more APIs for correct usage to speed up their development

[jeffhandley]

With the Roslyn Analyzers momentum we built in .NET 5 and .NET 6, we've found that developers benefit from analyzers that verify correct usage of .NET Libraries APIs. Continuing on the story from .NET 6 in #43617, we will continue working with the community to foster contributions into our collection of analyzers and code fixers.

Planned for .NET 7

• Analyzer / fixer proposal: Prefer static HashData methods over ComputeHash #40579
• Prefer Dictionary<K, V>.TryGetValue() over guarded indexer access #33798
• Don't guard Dictionary<K, V>.Remove(key) by ContainsKey(key) #33797
• Prefer ExactSpelling=true on [DllImport] for known APIs #35695
• Analyzer Proposal: Seal internal/private types #49944
• [Proposal] Analyzer that suggests ToUpperInvariant/ToLowerInvariant in place of ToUpper/ToLower #43976

Backlog (in roughly priority order)

• Prefer Dictionary<K, V>.TryAddValue(key) over guarded Add(key) #33799
• Proposal: Hide Thread.VolatileRead and Thread.VolatileWrite #27997
• Use AsParallel() correctly #33769
• Do not use OfType<T>() with impossible types #33770
• Extract array of const to static readonly field #33794
• Constructor parameters should match property names #33796
• Add analyzer: Prevent wrong usage of string Split #47927
• Prefer Span<T>.Clear() over Span<T>.Fill(default) #33813
• Prefer Dictionary.Remove(key, out value) over Dictionary.this[key], followed by Dictionary.Remove(key) #33800
• Avoid implicitly allocating params arrays in loops #33793
• Prefer static ReadOnlySpan<byte> properties over static readonly byte[] fields #33780
• Do not pass Utf8JsonReader by value #33772

Related Epics

• Port remaining FxCop rules into .NET as Roslyn Analyzers #61964