CLR via C#, Second Edition

Data Binding with Windows Forms 2.0 : Programming Smart Client Data Applications with .NET (Microsoft Net Development Series)

Pro C# 2005 and the .NET 2.0 Platform, Third Edition

Programming

Framework Design Guidelines : Conventions, Idioms, and Patterns for Reusable .NET Libraries (Microsoft Net Development Series)

Format: Hardcover
Author: Krzysztof Cwalina
ReleaseDate: 19 September, 2005
Publisher: Addison-Wesley Professional
Rating:

invaluable to developers of class libraries, components, and frameworks--whether .NET or not.
NET Review (wiki.
Excerpt from C# Online.CSharp-Online. NET):
"The book is a codification of the set of guidelines worked out by the Microsoft . NET Framework development team to govern the project. It has been refined over six years. It's like the Constitution of . NET. But, the guidelines are so well crafted that the principles embodied in them apply equally well, not only, to all . NET languages, but also, to Java or any object-oriented language. " .

A book of do's and dont's
This is just a book of do's and dont's. Just got this book. Literally. Just about every page says. . .

DO this.
DON'T do that.
DO that.
DON'T do this.

All the way through the book.

This is not my preferred reading style. I was expecting more tutorials and code examples of some successful object models, not just some rules where the key words to help you remember are repeated and in bold, "DO" and "DON'T".

Considering this was a five-star book and featured in magazines and various web sites, I am seriously disappointed.

I'm sure the actual rules being pointed out are fine. Great, even. Meriting of 3 stars instead of 1 or 2. But I don't think it likely for me to bother reading this book because it has no real structure, hence I don't see it enabling me to remember the points it was trying to make.

Great Guidelines for Framework or Library builders
From the first pages, I was able to apply suggestions to how I designed frameworks. I found the book immediately helpful. 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.
.