Analyzers prototyping - Representative analyzers set

[JanKrivanek]

Context

#9627

• Let's go through ideas and build interesting initial set
• Mark the analyzers in the set based on viability based on EventArgs ('Doable today', 'Doable with slight adjust of EventArgs with minimum implementation and perf cost', 'More complicated')
• Let's choose few from the first 2 categories above, Expose OM for them and author them

The main part should be the last point

FYI @ladipro (this is based on your suggestion)

References

• [Internal link] analyzer ideas

[JanKrivanek]

Candidates:

• Warning Waves Items
• Internal Ideas Dump

Top 3 by @rainersigwald:

• project-instance races with the same bin/obj
• double writes
• forbidding References to outputs of this repo (in favor of ProjectReferences)

Other top candidates:

• https://github.com/dotnet/msbuild/issues/9781
• Mixing TargetFramework and TargetFrameworks in a single project - very easy to check, and there is probably no logitimate usage for the case.

[ladipro]

Here's the list of analyzers we would like to ship, each with its own issue:

• #9879
• #9880
• #9881
• #9882
• #9883
• #9884
• #9885
• #9888
• #9889
• #9891
• #9892

I'll close this one and we'll continue in individual issues. Each proposed analyzer is a bit different and the devil is in the details, as they say.

[stan-sz]

This seems relevant to #1777