title: Code analysis check-in policy kills productivity when combined with Test-driven development
body: <p>We are working with VS2012+TFS2012 and I wanted to add code analysis check-in policy to remind every team members to fix code warnings before checking-in, but then I noticed it forces us to check "activate code analysis on build" project option.</p>
  
  <p>We are also doing TDD, so it means we code a unit test, run it (which means build the project) to confirm the test fails, we code to make the test passes, then we run the test again to confirm it passes. </p>
  
  <p>So for 1 unit test we have to build twice (minimum, sometimes more if we do some coding error), but because code analysis takes more than 10 sec to run on every build this is very very unproductive :(</p>
  
  <p>Is it possible to enforce running code analysis only before check-in, not on every build ?</p>