-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to treat NETSDK warnings as errors #2748
Comments
You can use the universal MSBuild flag with |
Thanks for the quick response! |
This still causes the build to exit with a success code when warnings occurs. :( |
@Crono1981 Might be better to open a new issue for that. Would probably give you a proper response faster. |
….2 (#2748) - Microsoft.NET.Sdk - 5.0.100-alpha1.19458.2
While updating to 2.2.100 I noticed a couple of warnings were added. Like
NETSDK1071
.In my CI I build using the
TreatWarningsAsErrors
flag (dotnet build /p:TreatWarningsAsErrors="true"
)`.The build still completed succesfully, while
NETSDK1071
was thrown.What is the recommended way to force a build to fail if any of these warnings are thrown from the SDK?
The most user friendly way would be to use the same flag as msbuild. But that doesn't seem to be supported atm.
The text was updated successfully, but these errors were encountered: