A new edition of this title is available, 0321545613 9780321545619 "This book is an absolute must-read for all .NET developers. It gives clear do and don't guidance on how to design class libraries for .NET. It also offers insight into the design and creation of .NET that really helps developers understand the reasons why things are the way they are. This information will aid developers designing their own class libraries and will also allow them to take advantage of the .NET class library more effectively." --Jeffrey Richter, author/trainer/consultant, Wintellect " Framework Design Guidelines will help you in two important ways. First, any .NET developer will benefit from a greater understanding of the design principles that govern the .NET Base Class Library. Second, a deeper understanding of these principles will help you to create software that integrates well with the .NET environment. Quite frankly, this book should be on every .NET developer's bookshelf." --Bill Wagner, founder and consultant, SRT Solutions, author of Effective C# "Not since Brooks' The Mythical Man Month has the major software maker of its time produced a book so full of relevant advice for the modern software developer. This book has a permanent place on my bookshelf and I consult it frequently." --George Byrkit, senior software engineer, Genomic Solutions "This book is a must-read for all architects and software developers thinking about frameworks. The book offers insight into some driving factors behind the design of the .NET Framework. It should be considered mandatory reading for anybody tasked with creating application frameworks." --Peter Winkler, senior software engineer, Balance Technology Inc. "Frameworks are valuable but notoriously difficult to Your every decision must be geared towards making them easy to be used correctly and difficult to be used incorrectly. This book takes you through a progression of recommendations that will eliminate many of those downstream 'I wish I'd known that earlier' moments. I wish I'd read it earlier." --Paul Besly, principal technologist, QA "Filled with information useful to developers and architects of all levels, this book provides practical guidelines and expert background information to get behind the rules. Framework Design Guidelines takes the already published guidelines to a higher level, and it is needed to write applications that integrate well in the .NET area." --Cristof Falk, software engineer Framework Design Conventions, Idioms, and Patterns for Reusable .NET Libraries teaches developers the best practices for designing system frameworks and reusable libraries for use with the Microsoft .NET Framework and WinFX. This book focuses on the design issues that directly affect the programmability of a framework, specifically its publicly accessible APIs. This book can improve the work of any .NET developer producing code that other developers will use. An added benefit is a collection of annotations to the guidelines by various members of the Microsoft .NET Framework and WinFX teams, which provide a lively discussion of the motives behind the guidelines, along with examples of good reasons for breaking the guidelines. Microsoft architects Krzysztof Cwalina and Brad Abrams offer guidelines for framework design from the top down. From their long experience and deep insight, you will learn Guidelines in this book come in four major Do , Consider , Avoid , and Do not . In general, a Do guideline should almost always be followed, a Consider guideline should generally be followed, an Avoid guideline indicates that something is generally not a good idea, and a Do not guideline indicates something you should almost never do. Every guideline includes a discussion of its applicability, and most guidelines include a code example. A companion DVD includes the Designing .NET Class Libraries video series, instructional presentations by the authors on design guidelines for developing classes and components that extend the .NET Framework. A sample API specification and other useful resources are also included.
This is the book that at least all .NET developers have to read! It mentioned tips, best-practices, and a lot of other things about .NET and framework design.
And it's good to remember what folks have reviewed this book: Anders Hejlsberg, Scott Guthrie, and Miguel De Icaza. You can learn a lot from each of them individually!
It gave me some insight into the though process that is behind .net framework, and it were interesting that they have included different viewpoints for the design decisions that were made.
This book is a must-read for any developer who is building or consuming .NET libraries. Even if you are familiar with the guidelines (from blogs, FxCop, or elsewhere) this book is outstanding--the authors sprinkle the primary guidelines content with commentary from other bigwigs, including Jeffrey Richter, Rico Mariani, Anders Hejlsberg and more. Through their comments, you get the "story-behind-the-story" (which guidelines are really important, which guidelines they disagree with, which guidelines are not followed the .NET Framework itself, etc.) This adds valuable practical advice, and makes for an interesting read.
The best resource around for API design. Based on the creation of the .NET framework APIs, this is a fantastic set of guidelines for helping developers create easily understood API signatures.
One of my favorite aspects is the break-out text by various additional contributors. They are not afraid to point out their own mistakes (many of which still exist within the .NET libraries) or to question each others' decisions. Since there is very rarely a single right or wrong solution to a problem, I appreciate the discussions and reasoning behind many of these choices.
Must read for .NET developer. It's aimed at explaining the rules for developing framework libraries but even if you're not in that business it's packed with insight. The book alternates between dry rules and entertaining commentary by .NET luminaries explaining exceptions, history or just why they miss Hungarian notation.
This book shows that the .net Framework has a clear design to it that is pretty decent and useful to follow Microsoft's lead. I recomend it to anyone working with .net.
A must read for every one how creates source code or is responsible for software quality. This was the eye opener for me for how to build quality into software.
Although nowadays maybe bit outdated but still has a lot of fascinating advices. Absolutely eye opening book and must read when you are a .net developer.