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

Debugging


There comes a time in every application's life where it will need to be debugged. A non-distributed application is usually easy to debug since you can simply execute it in a debugger. Once in the debugger, you can perform various actions that the debugger provides, such as breakpoints or stepping through code.

When dealing with distributed systems, since some of the systems are remote from one another, debugging can be a bit more challenging. One option is to make use of remote debugging. This involves installing debugging components on computers so that the system can be debugged remotely. Once configured, remote debugging is generally the same as local debugging. Remote debugging is fine for sandboxed and test environments, but is generally frowned upon in production or acceptance environments. Installing components other than those that are required to run the system is often denied.

Even when you can debug remotely, there may be so many processes in play that you cannot debug...