-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Common.targets doesn't promote TreatWarningsAsErrors to MSBuildTreatWarningsAsErrors #10871
Copy link
Copy link
Open
Labels
Priority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withouttriaged
Description
Common.targets does respect the "plain property" version of some warning-related settings:
msbuild/src/Tasks/Microsoft.Common.CurrentVersion.targets
Lines 668 to 672 in 69b3e7a
| <PropertyGroup> | |
| <MSBuildWarningsAsMessages Condition="'$(MSBuildWarningsAsMessages)'==''">$(NoWarn)</MSBuildWarningsAsMessages> | |
| <MSBuildWarningsAsErrors Condition="'$(MSBuildWarningsAsErrors)'==''">$(WarningsAsErrors)</MSBuildWarningsAsErrors> | |
| <MSBuildWarningsNotAsErrors Condition="'$(MSBuildWarningsNotAsErrors)'==''">$(WarningsNotAsErrors)</MSBuildWarningsNotAsErrors> | |
| </PropertyGroup> |
but it doesn't do the broader setting MSBuildTreatWarningsAsErrors in the same way.
This adds to the confusion about which settings to use.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Priority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withouttriaged