The SDM captures the basic invariant structure and behaviors of a system in a self-contained model. It provides the scaffolding to which other information can be applied. This may include deployment information, installation procedures, configuration schemas, automation
Through the SDK, the SDM encourages the creation of reusable, prescriptive models that can be easily incorporated into the application or hosting environment of Team Architect.
Visual Studio will extend design for deployment by enabling production deployment and operations management of distributed applications.
In this chapter and the
In this chapter, we'll focus on analyzing managed code, such as C# and VB.NET. If you're working with C or unmanaged C++,
We begin by discussing the origins of the Static Code Analysis tool. We'll introduce Microsoft's .NET Design Guidelines for Class Library Developers and describe how it is
Then we will describe the tool itself and how to take advantage of its full integration with Team System. This includes enabling Static Code Analysis review for your projects, selecting rules to apply, and working with the results of the analysis.
However, using the IDE is not always an option and sometimes you need additional flexibility. The Static Code Analysis tool is available to you from the command line. You will also learn how to use the command line for code analysis and how to include code analysis with your automated builds.
The Static Code Analysis rules that ship with Team System will probably not be sufficient for the specific standards and practices of your own projects. To address this, we will also describe how you can create and integrate new custom rules. We begin by describing the mechanics of rules, introducing the new Introspection engine. You will then create an example rule using introspection and call it from the Visual Studio IDE.
Ensuring that developers follow best practices and write consistent code is a major challenge in today's software development projects. The act of documenting standards and practices is often
One of the best resources available for .NET developers is Microsoft's .NET Framework "Design Guidelines for Class Library Developers." These guidelines document Microsoft's (formerly) internal practices for developing class libraries and are
The guidelines cover a wide range of subjects, including naming conventions, usage guidelines, and performance and security considerations. The importance of these guidelines cannot be overstated. When put into practice, they help ensure that your approach will be consistent with that of other developers. In addition, they have evolved over a number of
As useful as the design guidelines are, the reality of software creation is that many developers, due to lack of time or perhaps of interest, will not be familiar with their contents. The