Uh oh!
There was an error while loading. Please reload this page.
Included existing NoWarn value - #15444
Conversation
psfinaki
left a comment
There was a problem hiding this comment.
I think <NoWarn>$(NoWarn);(all the other warnings)</NoWarn> is the right approach.
nojaf
commented
Jun 20, 2023
@psfinaki I was more referring to the |
psfinaki
commented
Jun 20, 2023
Hmm I suspect MSBuild would default a random number to C# compiler warnings. I cannot find explicit docs on that, although these explanations kind of imply that. Either way, FS0075 is more safe and explicit. |
baronfel
commented
Jun 20, 2023
@psfinaki it's not an MSBuild behavior, rather Roslyn chooses to interpret pure numbers as having the CS prefix. This is not considered good practice anymore in a world of many different components providing diagnostics (analyzers, linker, nuget, etc) and so we should always fully qualify these days. |
I have an extra value
NoWarnvalue in myDirectory.Build.props.user.This would allow it to come through in
src/FSharp.Build/FSharp.Build.fsproj.PS: When do you use
<NoWarn>$(NoWarn);75</NoWarn>versus<NoWarn>FS0075</NoWarn>?