Book Image

Visual Studio 2010 Best Practices

By : Peter Ritchie
Book Image

Visual Studio 2010 Best Practices

By: Peter Ritchie

Overview of this book

When you are developing on the Microsoft platform, Visual Studio 2010 offers you a range of powerful tools and makes the whole process easier and faster. After learning it, if you are think that you can sit back and relax, you cannot be further away from truth. To beat the crowd, you need to be better than others, learn tips and tricks that other don't know yet. This book is a compilation of the best practices of programming with Visual Studio. Visual Studio 2010 best practices will take you through the practices that you need to master programming with .NET Framework. The book goes on to detail several practices involving many aspects of software development with Visual Studio. These practices include debugging and exception handling and design. It details building and maintaining a recommended practices library and the criteria by which to document recommended practices The book begins with practices on source code control (SCC). It includes different types of SCC and discusses how to choose them based on different scenarios. Advanced syntax in C# is then covered with practices covering generics, iterator methods, lambdas, and closures. The next set of practices focus on deployment as well as creating MSI deployments with Windows Installer XML (WiX)óincluding Windows applications and services. The book then takes you through practices for developing with WCF and Web Service. The software development lifecycle is completed with practices on testing like project structure, naming, and the different types of automated tests. Topics like test coverage, continuous testing and deployment, and mocking are included. Although this book uses Visual Studio as example, you can use these practices with any IDE.
Table of Contents (16 chapters)
Visual Studio 2010 Best Practices
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface

Round-tripping requirements and acceptance


One of the benefits of writing in .NET is that its managed code "compilation" produces an abstract intermediary language (IL). The results of this compilation are code and meta-information that we can analyze very easily and directly with .NET, using reflection or other tools via inspection of the generated IL or bytecode.

As tests and test classes are generally attributed with information around tests and test methods, we're free to search for and specifically analyze our tests in very useful ways.

One analysis, of course, involves static analysis of test to check for specific rules. There are various tools out that perform such tasks, such as FxCop or Visual Studio Code Analysis. We won't look too closely at those (I'll leave that as an exercise to the user).

One thing we can do with our tests is perform round-trip requirements and acceptance documentation.

The typical "waterfall" type approach is that you are given requirements, you implement...