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

Principles


To get an idea of what can be done, and thus what should be done with SCC, it's a good idea to briefly describe the principles of source code control:

  • Tracking: First and foremost, source code control deals with tracking changes. SCC systems generally track the deltas (just the changes) made from one commit to the next.

  • History: SCC keeps a history of what was done to each file for each commit. This includes date/time, user, changes, comments, and so on. This history allows users to see what has been done to the code in the past and thus supports the next principle.

  • Collaboration: SCC systems aid in collaboration by providing means to isolate the changes of one team member from another. These systems also provide very powerful tools to merge isolated changes together.

  • Auditing: SCC allows auditing of changes. Many systems have an annotate or blame feature that allows you to track the modification of a particular line in a particular file to a specific person. I don't...