-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Built-in analyzer] TargetFramework and TargetFrameworks are both set #9880
Copy link
Copy link
Closed
Labels
Area: BuildCheckBuildCheck SuggestionSuggestion for a built in MSBuild analyzer. Label should be applied together with 'Area: BuildCheck'Suggestion for a built in MSBuild analyzer. Label should be applied together with 'Area: BuildCheck'triaged
Description
Background
This issue tracks one of the BuildCheck analyzers we would like to ship in-box with MSBuild.
Goal
Implement an analyzer with the following rule: The TargetFramework and TargetFrameworks properties should not be both set in outer builds.
Notes
Setting both properties leads to unexpected SDK behavior. It is not uncommon for developers to define one of them in a project file and the other in an imported file such as Directory.Build.props.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: BuildCheckBuildCheck SuggestionSuggestion for a built in MSBuild analyzer. Label should be applied together with 'Area: BuildCheck'Suggestion for a built in MSBuild analyzer. Label should be applied together with 'Area: BuildCheck'triaged
Type
Fields
Give feedbackNo fields configured for issues without a type.