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

First principles


Any practice worth its salt in terms of its applicability and correctness are often guided by a set of principles or goals, as it were, that the practices are trying to adhere to or accomplish. Automated testing is no different. Automated testing has certain goals that it is expected to accomplish and our practices revolve around accomplishing those goals.

Related terms

In any effective conversation, a consistent vocabulary is vital to communication. So, let's quickly get some terms out of the way:

  • Unit test: An automated test that tests a single unit of source code. Unit is a bit subjective and often means module in many circles, but could be as narrow as a class or a method.

  • Integration test: An automated test that validates the interaction of combined modules.

  • Test fixture: In the context of automated testing and unit testing frameworks, this is the class or the class hierarchy where test methods live.

  • System under test (SUT): What is being tested? This could be...