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

Distributed architecture


With the advent of big data and multi-core machines, it becomes apparent that in order to keep up with the amount of data, we need to begin scaling our systems out.

Although making use of multiple cores simultaneously (that is, in parallel) is effectively considered scaling up (or vertical scalability), some of the principles we can use to reliably do this can be applied to scaling out (or horizontal scalability).

One of the difficult parts of multithreaded programming is the synchronization of shared data. Data that can be read and written in two different places at the same time needs to make sure those operations don't overlap across threads and corrupt data. This is the act of making something Thread Safe or writing code for thread synchronization. This process is tricky and sometimes hard to get right. More detail on this can be found in Chapter 8,Parallelization Practices.

Another difficult part of multithreaded programming and distributed design is the separation...