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

Logging


Subsystems, and systems in a distributed system, have a high level of independence. A message sent by one subsystem occurs asynchronously. The send of a message does not occur at or near the receipt of that message on the other end. If the intended receiver of that message was unable to receive that message, it could be an astoundingly lengthy amount of time (as in seconds) before the loss of the message is detected. However, when you are looking at even 500 transactions per second throughput, a few seconds is a lot of data to wade through to figure out when the problem occurred and with what data.

Logging is vital to being able to track down problems in a distributed system.

There are logging frameworks and tools that do all sorts of different types of logging, and abstracts away the details of different types of logs. I recommend using some sort of logging framework to abstract where you want to log, from the fact that you are logging. For example, you may want to sometimes log...