ValueTask, the analyzers are misfiring saying I shouldn't use the Async suffix on method names that return
ValueTask. The vs-threading analyzers already do some of what the 3 analyzers in this project do, so I'm trying to decide whether I should invest time in a PR for this project to add support for
ValueTaskat least (and hope the PR is accepted and a new version published to nuget.org) or just abandon use of this package and add the equivalent functionality to vs-threading.
Microsoft.VisualStudio.Threading.Analyzersalready is a proper superset of AsyncUsageAnalyzers. We filled in the remaining gaps (Microsoft/vs-threading#382) in our 15.8.168 release.
Microsoft.VisualStudio.Threadinglibrary as well, although it's possible some rules will suggest fixes that don't apply to your app yet, in which case you can turn off those individual rules (and please file a bug if you notice this happening). As for the documentation, and a way to automatically set up appropriate default rulesets per app-type, that's something we're working on.
AsyncFixer Microsoft.CodeAnalysis.CSharp Microsoft.CodeAnalysis.CSharp.Workspaces Microsoft.CodeAnalysis.FxCopAnalyzers Microsoft.DotNet.Analyzers.Compatibility StyleCop.Analyzers ToStringWithoutOverrideAnalyzer
Microsoft.VisualStudio.Threading.Analyzers IDisposableAnalyzers ReflectionAnalyzers