title: "Treat all warnings as errors except..." in Visual Studio
body: <p>In Visual Studio, I can select the "Treat warnings as errors" option to prevent my code from compiling if there are any warnings. Our team uses this option, but there are two warnings we would like to keep as warnings. </p>
  
  <p>There is an option to suppress warnings, but we DO want them to show up as warnings, so that won't work.</p>
  
  <p>It appears that the only way to get the behavior we want is to enter a list of every C# warning number into the "Specific warnings" text box, except for the two we want treated as warnings.</p>
  
  <p>Besides the maintenance headache, the biggest disadvantage to this approach is that a few warnings do not have numbers, so they can't be referenced explicitly. For example, "Could not resolve this reference. Could not locate assembly 'Data....'"</p>
  
  <p>Does anyone know of a better way to do this?</p>
  
  <hr>
  
  <p>Clarifying for those who don't see immediately why this is useful. Think about how most warnings work. They tell you something is a little off in the code you just wrote. It takes about 10 seconds to fix them, and that keeps the code base cleaner.</p>
  
  <p>The "Obsolete" warning is very different from this. Sometimes fixing it means just consuming a new method signature. But if an entire class is obsolete, and you have usage of it scattered through hundreds of thousands of lines of code, it could take weeks or more to fix. You don't want the build to be broken for that long, but you definitely DO want to see a warning about it. This isn't just a hypothetical case--this has happened to us.</p>
  
  <p>Literal "#warning" warnings are also unique. I often <em>want</em> to check it in, but I don't want to break the build.</p>