http://blogs.msdn.com/b/codeanalysis/archive/2007/08/08/_24002800_codeanalysistreatwarningaserrors_2900_-msbuild-property.aspxFor Visual Studio 2008, we have added a new MSBuild property that allows you to easily treat all Code Analysis warnings as build errors. This can be useful for example, if you want to force that any firing of a Code Analysis rule to break the build duringen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/codeanalysis/archive/2007/08/08/_24002800_codeanalysistreatwarningaserrors_2900_-msbuild-property.aspx#6481838Fri, 23 Nov 2007 13:22:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:6481838From the software development trenches<p>In previous posts about Code Metrics and Code Reviews , I explored some metrics and techniques that I</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=6481838" width="1" height="1">http://blogs.msdn.com/b/codeanalysis/archive/2007/08/08/_24002800_codeanalysistreatwarningaserrors_2900_-msbuild-property.aspx#4297773Thu, 09 Aug 2007 00:18:48 GMT91d46819-8472-40ad-a661-2c78acb4018c:4297773Chris Conti<p>In VS2008, is integrated code analysis still relegated to the Team editions of VS? FxCop? /analyze (C++)? (If I ever get a free moment, I'll actually install Beta 2 and check for myself...)</p> <p>I've always failed to understand the tying to the Team editions as both FxCop and PREFast are freely available (The Vista SDK includes a C++ compiler with /analyze enabled).</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=4297773" width="1" height="1">