Steven John Metsker explains how to use C# as an object-oriented language, using design patterns to create clean code while taking advantage of the extensive Microsoft(R) .NET Framework Class Libraries.

For all 23 classic "Gang of Four" design patterns, Metsker offers detailed code examples utilizing C# and the .NET Framework--as well as programming exercises crafted to help you rapidly build expertise. His exercises and explanations make extensive use of the Unified Modeling Language, helping you build your skills in this standard notation.

Design patterns covered include:

• Interfaces: Adapter, Facade, Composite, and Bridge

• Responsibility: Singleton, Observer, Mediator, Proxy, Chain of Responsibility, and Flyweight

• Construction: Builder, Factory Method, Abstract Factory, Prototype, and Memento

• Extensions: Decorator, Iterator, and Visitor

If you've already used design patterns in other languages, Design Patterns in C# will deepen your understanding, build your confidence, and help you apply them to any C# project. If you're a Microsoft programmer who's new to design patterns, this book will be an ideal practical introduction.

www.awprofessional.com/patterns/

ADDISON-WESLEY PROFESSIONAL

Pearson Education

ISBN: 0-321-12697-1

Amazon.com® Reader Reviews (Ranked by Helpfulness)

Average Amazon.com® Rating:  Based on 31 Ratings

Why only 1 star??? - 2007-03-09
Reviewer Rating:
Honesty I think this book is great and yes there are aspects of the book that could be improved but overall its still a great book. I think if you are serious about becoming a PRO software engineer, you should checkout this book. More books like this should be written to help programmers grasp the more complex area of OOP.

This book is not for beginners, you must have a fairly good understanding of GOF design patterns in order to help you consolidate your knowledge.

Unfortunate news! - 2009-02-25
Reviewer Rating:
For those who didn't know, the author of this book, Steven John Metsker, passed away on February 2008. The news was posted on his web site (http://xp123.com/oozinoz/). I love his books, and wish to have a fraction of his talent! I am sadden to learn this bad news.

Ugh, Such a Textbook - 2008-11-03
Reviewer Rating:
I got this book because it was the only book on design patterns at the bookstore; maybe I should have browsed Amazon instead! My first impressions is that it is dry, abstract, old-fashioned, even occasionally pedantic. He seems to skip the basics of each pattern, perhaps assuming that the reader is already familiar.

I write software for a living, I know how important good design is, but Metsker seems to think we'll just take his word for it when he claims that such-and-such a design is the Only Correct Way. How about some examples of how each pattern could solve real design problems?

While I found them tiresome, the quizzes sprinkled throughout may be useful for new programmers. But if they take this book to heart, they may "learn" that there's always one (and only one) correct solution to a problem. Real development is not so simple.

Not a substitute for Gof Design Patterns Book - 2007-08-06
Reviewer Rating:
Well, I have to say after reading most of the book, that it's not what I expected. Being very familiar with "Design Patters" I was hopeful that this book would give some concrete examples in C#. Instead, it's more of a text book that asks you to fill in the blanks. This type of book is useless as a reference.

Get the real "Design Patterns" book. It's more of a reference book and is something you will keep on your desk for a long time to come.

Excellent Companion to GoF Design Patters - 2007-06-15
Reviewer Rating:
I found the GoF book to be to conceptual and I had a difficult time imagining how I would actually implement the patterns in a specific application. I love the GoF book, but it is a difficult read.

This book was exactly what I needed to answer most of my questions. I still have some, but hopefully, working through my own implementations I will get some possible answers for those.

I like some of the challenges, as it is possible to read and think you understand something only to find yourself unable to explain it to someone else or to implement it. If you can work through the challenges, you can be sure that you have a good understanding of the material.
Some of the challenges were just silly word puzzles, but someone out there probably enjoys those.

Browse Similar Topics

Top Level Categories:
Software Engineering

Sub-Categories:
Software Engineering > Design Patterns