Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Visual Studio 2010 Best Practices Paperback – August 24, 2012
|New from||Used from|
Top 20 lists in Books
View the top 20 best sellers of all time, the most reviewed books of all time and some of our editors' favorite picks. Learn more
About the Author
Peter Ritchie is a software development consultant. Peter is president of Peter Ritchie Inc. Software Consulting Co., a software consulting company in Canada's National Capital Region specializing in Windows-based software development management, process, and implementation consulting. Peter has worked with such clients as Mitel, Nortel, Passport Canada, and Innvapost from mentoring to architecture to implementation. Peter has considerable experience building software development teams and working with startups towards agile software development.
Peter's range of experience ranges from designing and implementing simple standalone applications to architecting distributed n-tier applications spanning dozens of computers; from C++ to C#. Peter is active in the software development community attending and speaking at various events as well as authoring various works including Refactoring with Microsoft Visual Studio 2010.
More About the Author
Top Customer Reviews
At the high level, any programmer would do well to ruminate on Ritchie's remarks. Like avoiding pragmatic re-use. This refers to the very common practice of a programmer finding sample code and then bunging it into her existing program. Without perhaps carefully parsing to check for unintended side effects. You should be doing the latter anyway, if you are experienced enough.
Another piece of advice is to avoid the not invented here syndrome. This refers to when a piece of functionality is available externally to your company. But because it was not written inside the firm, you decide not to use it and proceed to reimplement the functionality yourself. There are several drawbacks. The first is the amount of time you or your co-workers will need. The second is that perhaps the resulting code will not have been well tested. Especially if it is new code, after all. Whereas suppose there is indeed an external library that you know to have been written and extensively tested by a reputable organisation. You should think carefully before writing your own supposedly equivalent package. Ask yourself where you can best add value. It usually is not in replicating others' work.
Another section of the text talks about source code control practices. What has happened in recent years is that third party websites have sprung up that offer server hosting for this. Including github, bitbucket and phase2.Read more ›
In fairness I also know the author Peter having seen him speak at DevTeach on many occasions. I started by looking at the table of content to see what this book was about, knowing that "best practices" is a real misnomer I wanted to see what they were. I really like the fact that he starts the book by really saying they are not really best practices but actually recommend practices.
As a Team Foundation Server user I found that chapter 2 was more for the open source crowd and I really skimmed it. The portion on Branching was well documented, although I'm not a fan of the testing branch myself, but the rest was right on. The section on merge remote changes (bring the outside to you) paradigm is really important and was touched on.
Chapter 3 has good solid practices on low level constructs like generics and exceptions.
Chapter 4 dives into architectural practices like decoupling, distributed architecture and data based architecture. DTOs and ORMs are touched on briefly as is NoSQL.
Chapter 5 is about deployment and is really a great primer on all the "packaging" technologies like Visual Studio Setup and Deployment (depreciated in 2012), Click Once and WIX the major player outside of commercial solutions. This is a nice section on how to move from VSSD to WIX this is going to be important in the coming years due to the fact that VS 2012 doesn't support VSSD.
In chapter 6 we dive into automated testing practices, including test coverage, mocking, TDD, SpecDD and Continuous Testing. Peter covers all those concepts really nicely albeit succinctly. Being a book on recommended practices I find this is really good.Read more ›
The book covers various aspects of visual studio, going from Source control, Programming, Deployment, Automated Testing and more.
Each of the topics is well detailled, starts with a nice overview and is easy to read.
Looking deeper into the domain of QA and automated testing, chapter 6 covers how to facilitate Visual Studio for test driven and behavior driven development and the importance of automated testing.
Overall a interesting read with some great tips and tricks.
"I call them 'recommended practices' instead of 'best practices'. The superlative 'best' implies some degree of completeness. In almost all circumstances, the completeness of these practices has a shelf-life. Some best practices have a very small shelf-life due to the degree to which technology and our knowledge of it changes."
While this is not an introduction to Visual Studio or the .NET Framework, most Visual Studio developers should find this book useful. Those who are less experienced with .NET will be able to take these recommended practices to get into the world of .NET on the right foot. Even those developers who consider themselves experts in Visual Studio will probably find some new nuggets of wisdom.
The practices discussed in the book range from architecture to C# language features to toolsets. Each recommendation is discussed with examples and then distilled down to two statements, a Context and a Practice. Here's an example around data transfer and messaging:
"Context: When dealing with data that needs to be actioned independently and asynchronously.
Practice: Consider command classes."
I have over 17 years developing with Microsoft tools, and I enjoyed reading Visual Studio 2010 Best Practices. I recommend reading it cover-to-cover and then keeping it on hand as a reference guide.
Most Recent Customer Reviews
As mentioned in another review, this book provides sound advice that is applicable far beyond just the use of Visual Studio. Read morePublished on November 29, 2012 by Gary I Varga
I'm in the process of reading the Visual Studio 2010 Best Practices eBook published by Packt Publishing: [... Read morePublished on November 17, 2012 by Steven J. Ackerman
The title of the book says Visual Studio 2010 best practices but that can be misleading as the practices are on software development as a whole not just to 2010. Read morePublished on November 13, 2012 by Rene Rendon Jr