Geek Answers Handbook

How can I suppress static code analysis during build?

We have a solution with 15 projects, all of which have code analysis.

The solution easily takes 60 seconds to build, which is a very long wait time waiting.

If I turn off code analysis, it will be created in 10 sessions.

I would like to be able to disable code analysis on a one-time basis. But still, I want the analysis of the code during creation before registration, and I also want our build server (Cruise Control) to continue to work with the included analysis of the code.

I would prefer if code analysis is started in Visual Studio, so I can go directly to the source code if I get an error / warning.

+4
source share
2 answers

Here's how we do it:

  • Disable (or rather: do not enable) Code Analysis (CA) for debug collections.
  • Create a new build configuration called Verify, where code analysis is enabled, and warnings are treated as errors.
  • Save the issue as is.

We are doing the usual development in debug mode and just have an informal rule that you must pass to the Verify assembly before registering.

It’s easy to forget, but we run Continuous Integration (CI) in the Verify assembly, so if you check the code with code analysis warnings, you break the assembly, so people quickly learned how to manually verify the assembly before checking :)

You can also use Debug without CA and Release with CA, but since the inclusion of CA defines the constant CODE_ANALYSIS, this means that CA Suppressions will be included in IL, and I prefer not to have this in my binary versions (YMMV).

+9
source

We had such a problem with our things. We got only four 64-bit processors and from 8 to 16 GB. Plus, we tried to limit the number of projects at any point. Not the most elegant solution, but it really helped.

+1
source

More articles:


All Articles