Context

Identified by MSBuild team as possible NET 9 topic
Motivation - automated way to educate users and give them tooling to improve their build recipes. Currently MSBuild team knows about various undesirable usage patterns, but have a little way of flagging those - in order not to break customers.

Some already collected ideas:

• [Internal link] potential analyzer ideas
• https://github.com/dotnet/msbuild/issues?q=is%3Aissue+is%3Aopen+label%3A%22Feature%3A+Warning+Waves%22+
• https://github.com/dotnet/msbuild/issues?q=is%3Aopen+is%3Aissue+label%3A%22Area%3A+Debuggability%22

Goals

• Collect requirements - mainly in regards of what should be analyzed, but as well ideas on how and when or even how to extend / plug-in
• Based on those put together quick informal design and run it through with PM/team - arrive to some conclusion on proposed design
• Create quick prototype/spike demonstratng the idea and few sample (may be dummy) built-in analyzer rules and idealy a pluggable rule

Tasks:

• Investigate and categorize existing MSBuild analyzing logic - Exchange #9421
• Investigate and categorize existing MSBuild analyzing logic - Roslyn, StructuredLogViewer #9422
• Investigate and categorize existing MSBuild analyzing logic - Suggested rules #9460