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

Data-based applications


It's hard to write software that doesn't deal with some sort of data that needs to be processed, stored, retrieved, and displayed in some form or another. While technologies that store data have only begun to change recently, frameworks to access these technologies change very frequently. Someone once quipped that Microsoft data development technology changes every four years. While this trend seems to have slowed in recent years, there's a trend away from relational data (the type of data these data development technologies interface with) towards non-relational data and "big data." One could argue that we're in the shadow of yet another data access framework from Microsoft. Regardless, we want to decouple our dependence on a particular framework or a particular data storage technology in as many places as possible.

While we're not particularly designing or architecting a system to support changing a data framework or changing a data store on-the-fly, we want to...