-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Analyzers prototyping - Representative analyzers set #9630
Copy link
Copy link
Closed
Labels
Description
Context
- 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
Work to be done for the first set of analyzers:
- [Built-in analyzer] Multiple projects share the same obj/bin #9879
- [Built-in analyzer] TargetFramework and TargetFrameworks are both set #9880
- [Built-in analyzer] The same file is written by multiple tasks during the build #9881
- [Built-in analyzer] EmbeddedResource item is missing the Culture metadata #9882
- [Built-in analyzer] Undefined property is used #9883
- [Built-in analyzer] Item is updated inside a target #9884
- [Built-in analyzer] Build depends on an environment variable #9885
- [Built-in analyzer] Reference item points to the output of a project #9888
- [Built-in analyzer] MSBuild task with BuildInParallel is batched #9889
- [Built-in analyzer] Property that starts with an underscore is set #9891
- [Built-in analyzer] String comparison is not properly quoted #9892
Condidates for followup set:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Fields
Give feedbackNo fields configured for issues without a type.