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

Division of labor


Of course, we really haven't shown truly parallel processing. We've shown how to make use of completion ports and not cause the main thread to be unresponsive. This really isn't doing two things at once when it comes to the cores in our system. We have multiple cores and we can use all of them to their full potential!

The real trick to making use of all your processors is your ability to divide up the work to be done, so that it can be offloaded, in parts, to each core. If you have an existing application and you're not already dividing up the work, this may be hard to do. You may already be dividing up the work within your application that we could possibly change to make use of multiple cores.

This book isn't a tome on parallelization of work, how to divide work by separating data involved in to units of work, and so on. The parallelization examples we'll detail here fall under the pattern of "embarrassingly parallel," which is code that is so obviously parallelizable as...