Skip to main content
  • 337 Accesses

Summary

In this chapter, you learned how to perform static code analysis to identify potential problem areas and known defects. Using the PREfast tool, you can eliminate a majority of the problems that may cause your code to have potential security holes and other instabilities. You can suppress messages and ensure that some messages are treated as warnings and others are treated as errors. On the whole, this makes working with C/C++ code much safer.

With the FxCop tool, you can ensure that your code is compliant with the latest Microsoft specifications for writing .NET code. This provides a well-structured, robust code base, which you can expand easily. In addition, as an organization using this tool to enforce coding standards specific to your needs, you can provide custom rules or more advanced rule checking than the defaults provided by FxCop. Combined with the check-in policy feature of VSTS (discussed in Chapter 3), FxCop can ensure that code created with VSTS conforms to your organization’s standards.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Similar content being viewed by others

Rights and permissions

Reprints and permissions

Copyright information

© 2006 Jeff Levinson and David Nelson

About this chapter

Cite this chapter

(2006). Static Code Analysis. In: Pro Visual Studio 2005 Team System. Apress. https://doi.org/10.1007/978-1-4302-0171-7_13

Download citation

Publish with us

Policies and ethics