Spotlight customer reviews:
|
Customer Rating: 
Summary: Great Guidelines for Framework or Library builders
Comment: I found the book immediately helpful. From the first pages, I was able to apply suggestions to how I designed frameworks. I have been creating .Net libraries since 2002. Now as the Lead Architect, my job is to create an entire product framework from the ground up.
My first decision was to ensure that my team had a set of guidelines. I searched the internet and this book came up on Amazon. I purchased the book, and found it immediately helpful. The authors have hand-on experience writing components of the .Net framework. They have learned through trial and error what works best. This book with some minor additions will serve as the guideline for my team.
You will find the book easy to read, clear and concise. In short the specifications of DO, DO NOT, CONSIDER, helped me understand the best practices for creating frameworks. As I read the guidelines, I also uncovered weakness in my understanding, particularly with the 2.0 framework. In these cases, the guidelines served as a target for additional learning.
I agree with the others, this book is not just for .Net frameworks. These are excellent guidelines for any object oriented language; although the book is directly effective for professionals that use the .Net framework.
Customer Rating:
Summary: Useful Guidelines for any System (not just .NET)
Comment: This is an extremely valuable multi-faceted discussion of how to name your classes and methods -- and how to structure your interfaces for ease of use and evolution over time.
The authors are thoughtful and clear in their reasoning and highlight their own "lessons learned" with real examples of shipped code that in retrospect could have been done better.
Customer Rating:
Summary: Goes beyond .NET
Comment: Even though this book has ".NET" in the name, it really reaches way beyond .NET and applies equally to Java or any other high-level object oriented language. Also, it is not just architects or designers who should read this book. Every developer trying to understand or even just use any kind of framework will benefit from it and gain deeper understanding why things are built the way they are built. Besides, the time comes in life of every developer when all of a sudden you must write your first framework, a set of base classes or whatever shared piece of code. At this moment you will thank yourself for having read this book (and still having it at reach if possible).
WARNING: this book requires some previous knowledge of object-oriented programming and familiarity with a C-like language (code samples are in C#, but any similar language will do). Also, keep in mind that this book is about design and concepts and not about C# or any particular .NET framework feature (although one can pick up some very useful tips along the way).
This is one of the two books that haven't left my desk ever since I bought them (the other one being "Head First Design Patterns" from Eric and Elisabeth Freeman).
Customer Rating: 
Summary: Design conventions and idioms for .NET libraries
Comment: As an outstanding member of the Microsoft .NET development series from Addison Wesley, this book examines the core issues you should address when designing public APIs with plenty of examples in C#.
After dealing with some general design principles and the philosophy behind the design of the Microsoft .NET Framework, the core of this book revolves around consistency guidelines for the .NET API design, from naming conventions (when to use Pascal casing and when to use camel casing) to the proper use of exceptions, from where to choose structs, classes, or interfaces to how to use properties, events, and operator overloads.
If you work with .NET, this book is an invaluable resource that explains the rationale behind the proposed guidelines. If you don't, you can still benefit from many of the guidelines.
Many comments from distinguished Microsoft employees make of this book an easy-to-read document you will surely enjoy. They even tell you where their designs were not right when they shipped the .NET Framework and, due to backward compatibility requirements, they were forced to live with their mistakes.
Customer Rating:
Summary: Perfect book for architecting frameworks
Comment: Book has perfect guidelines for the "layout" of designing a framework.
|
|
|
