I worked on some fairly large C# projects where the teams had zero-warning policies. It&#x27;s not that difficult to achieve with a bit of discipline. Warnings in third-party dependencies only show up if you build them from source, but these days it&#x27;s a lot easier to get your third-party dependencies from NuGet instead.<p>That being said, I don&#x27;t think warnings would be a good way to go on this case, because the sheer number of warnings generated by these new rules in existing, large (and mostly bug-free) projects would make it very difficult to reestablish a zero-warnings state. Developers on the team will just get undisciplined due the the broken windows effect.