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

Health monitoring


No matter what level of detail you have in logging, it does not do any good if no one knows to look in the log.

There are various tools to help monitor the computers and systems within an enterprise. Historically, this was done with Microsoft Operations Manager. Microsoft System Center now includes Operations Manager. These applications are designed to monitor computers, applications, and systems, and get current status and inform people of anomalous situations.

So, what has this got to do with the system you want to build? Well, Operations Manager is extensible and can be extended to do something specific to your application. Nevertheless, this development is time-consuming, and unless your system adds value to the system monitoring space, this might not be an efficient use of the development resources. Not to mention the ramp up and training time required for users of System Center to work with your system. Despite Operations Manager's extensibility, it supports the ability...