- Hardcover: 480 pages
- Publisher: Addison-Wesley Professional; 2 edition (November 1, 2008)
- Language: English
- ISBN-10: 0321545613
- ISBN-13: 978-0321545619
- Product Dimensions: 7.4 x 1.3 x 9.5 inches
- Shipping Weight: 2.1 pounds
- Average Customer Review: 22 customer reviews
- Amazon Best Sellers Rank: #674,337 in Books (See Top 100 in Books)
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 mobile phone number.
Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries (2nd Edition) 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2017 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
Customers who bought this item also bought
Customers who viewed this item also viewed
“Framework Design Guidelines is one of those rare books that can be read at different reading levels and can be useful to different kinds of developers. Regardless of whether you want to design an effective object model, improve your understanding of the .NET Framework, borrow from the experience of software gurus, stay clear of the most common programming mistakes, or just get an idea of the huge effort that led to the .NET initiative, this book is a must-read.”
—Francesco Balena, The VB Migration Partner Team (www.vbmigration.com), Code Architect, Author, and Microsoft Regional Director, Italy
“Frameworks are valuable but notoriously difficult to construct: your every decision must be geared toward 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
“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
“Updated for the new language features of the .NET Framework 3.0 and 3.5, this book continues to be the definitive resource for .NET developers and architects who are designing class library frameworks. Some of the existing guidelines have been expanded with new annotations and more detail, and new guidance covering such features as extension methods and nullable types has also been included. The guidance will help any developer write clearer and more understandable code, while the annotations provide invaluable insight into some of the design decisions that made the .NET Framework what it is today.”
—Scott Dorman, Microsoft MVP and President, Tampa Bay International Association of Software Architects
“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
“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
“The second edition of Framework Design Guidelines gives you new, important insight into designing your own class libraries: Abrams and Cwalina frankly discuss the challenges of adding new features to shipping versions of their products with minimal impact on existing code. You’ll find great examples of how to create version N+1 of your software by learning how the .NET class library team
created versions 2.0, 3.0, and 3.5 of the .NET library. They were able to add generics, WCF, WPF, WF, and LINQ with minimal impact on the existing APIs, even providing capabilities for customers wanting to use only some of the new features, while still maintaining compatibility with the original library.”
—Bill Wagner, Founder and Consultant, SRT Solutions, author of Effective C# and More Effective C#
“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, Sr. Software Engineer, Balance Technology Inc.
“An instant classic.”
—From the Foreword by Miguel de Icaza
About the Author
Brad Abrams was a founding member of the Common Language Runtime and .NET Framework teams at Microsoft Corporation. He has been designing parts of the .NET Framework since 1998 and is currently Group Program Manager of the .NET Framework team. Brad started his framework design career building the Base Class Library (BCL) that ships as a core part of the .NET Framework. Brad was also the lead editor on the Common Language Specification (CLS), the .NET Framework Design Guidelines, and the libraries in the ECMA\ISO CLI Standard. Brad has authored and coauthored multiple publications, including Programming in the .NET Environment and .NET Framework Standard Library Annotated Reference, Volumes 1 and 2. Brad graduated from North Carolina State University with a B.S. in computer science. You can find his most recent musings on his blog at http://blogs.msdn.com/BradA.
Krzysztof Cwalina is a program manager on the .NET Framework team at Microsoft. He was a founding member of the .NET Framework team and throughout his career has designed many .NET Framework APIs and framework development tools, such as FxCop. He is currently leading a companywide effort to develop, promote, and apply framework design and architectural guidelines to the .NET Framework. He is also leading the team responsible for delivering core .NET Framework APIs. Krzysztof graduated with a B.S. and an M.S. in computer science from the University of Iowa. You can find his blog at http://blogs.msdn.com/kcwalina.
Top customer reviews
It fully describes how and why the .NET framework is laid out the way it is, why the parts that seem to annoy you the most got it wrong and how, and provides many useful guidelines from helping you refrain from shooting yourself in the foot.
I might also say that it's equally applicable to just about any modern, sort of OO-based procedural language, but that would probably result in bloody religious wars.
The book is a series of guidelines, and then callouts from various contributors to the framework of why they like or dislike the rule. And in some cases very frank revelations about where they broke the rule and have now come to regret it. I like that format as most of the authors seemed to be very willing to discuss the frameworks mess ups and not just point to the parts they got right. It makes it seem much more human and approachable to me now.
There is not a lot of examples in the book though, it is mostly about building a style and set of guidelines for your application framework. I think this would make a great read for entry level programmers to help them understand the why you don't allow them to change the way things are exposed publicly, or to programmers who are looking to start designing APIs and are just looking for guidance. It is not a concrete how to build an API for doing "sometask". It is all about the theory behind API design and why you should employ the rules.
I have experienced many of the pains they explain in the book first hand (especially about Interfaces). Wish I would have read it before I released the first version of our API. I am implementing some changes based upon what I have read here, so it is definately a worthy book for those looking to take their design skills a little further.
One other thing I'll mention about this book is that it is geared toward developing a public API, so many of the recommendations may not be applicable to your specific situation. Indeed, for the development of most apps that aren't going to be used by other developers, much simpler coding approaches and architectures can and should be used. Despite that, however, this book has a lot going for it and you'll certainly gain a much deeper understanding of .NET after reading it.
Known inconsistencies and ambiguities are called out and explained, sometimes apologetically, as the gods of dotnet expound principles and then explain their own acts of creation to illustrate best practice - or sometimes worst practice, when they failed to heed their own advice. The text is littered with inset comments, as though the authors were standing around reviewing a draught of the book with you. They don't always share opinions, and the voice of dissent is as instructive as the explications.
I bought the first edition and loved it, giving it into the hands of someone who needed it. Now I have the second edition. Every now and then I skim it just to refresh my understanding, and sometimes to glean new insight in the context of more experience. Few of us will ever write an application framework, yet I think all of us would be better programmers if we shared the wisdom of those who do. Buy the book. If nothing else it's a hell of a conversation piece.
Lastly, the included DVD is just a presentation that can be found easily online, so it's nothing to be excited about. If you're looking to become a better API designer, or a better programmer, the book is a must-have. On the other hand, if you're a novice, you'd want to maybe hold off buying until you've understand the basics of OO and programming in general.