Problem solve Get help with specific problems with your technologies, process and projects.

Managed Code Analysis: Ch. 8 of Professional Visual Studio 2005 Team System

This chapter discuss Team System's Static Code Analysis tool, which checks both VB.NET and C# code for adherence to design guidelines and best practices.

Microsoft's Visual Studio 2005 Team System (VSTS) encourages collaboration throughout the software development lifecycle. Separate editions of the product exist for testers, developers, architects and database professionals (or "data dudes").

Professional Visual Studio 2005 Team System offers an overview of the product. The authors then present guidance for using VSTS for modeling, designing, and coordinating enterprise solutions. There are also hints for getting the most out of development scenarios and automation scripting in VSTS.

Chapter 8, Managed Code Analysis, focuses on how to use Team System's Static Code Analysis tool for C# or VB.NET code. This tool checks code for adherence to Microsoft's .NET Framework Design Guidelines. Static Code Analysis is available from both the Visual Studio IDE and from the command line, and the authors cover both instances. The chapter ends with hints for creating custom rules for the code analysis tool.

Read the rest of the excerpt in this PDF.

MORE: Click here to read Chapter 14 of this book, "Unit Testing with the Unit Test Framework."


Excerpted from the Wrox Press book, Professional Visual Studio 2005 Team System (ISBN 0-7645-8436-7) by Jean-Luc David, Tony Loton, Erik Gunvaldson, Christopher Bowen, Noah Coad and Darren Jefford.
Copyright © Nov. 15, 2006. Published by  John Wiley & Sons Inc.. Reprinted with permission.

Dig Deeper on Team development with Visual Studio Team System

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.