Framework Design Guidelines

Framework Design Guidelines : Conventions, Idioms, and Patterns for Reusable .NET Libraries

4.18 (282 ratings by Goodreads)
By (author)  , By (author) 

List price: US$64.99

Currently unavailable

We can notify you when this item is back in stock

Add to wishlist

AbeBooks may have this title (opens in new window).

Try AbeBooks

Description

Framework Design Guidelines, Second Edition, teaches developers the best practices for designing reusable libraries for the Microsoft .NET Framework. Expanded and updated for .NET 3.5, this new edition focuses on the design issues that directly affect the programmability of a class library, specifically its publicly accessible APIs. This book can improve the work of any .NET developer producing code that other developers will use. It includes copious annotations to the guidelines by thirty-five prominent architects and practitioners of the .NET Framework, providing a lively discussion of the reasons for the guidelines as well as examples of when to break those guidelines. Microsoft architects Krzysztof Cwalina and Brad Abrams teach framework design from the top down. From their significant combined experience and deep insight, you will learnThe general philosophy and fundamental principles of framework design Naming guidelines for the various parts of a framework Guidelines for the design and extending of types and members of types Issues affecting-and guidelines for ensuring-extensibility How (and how not) to design exceptions Guidelines for-and examples of-common framework design patternsGuidelines in this book are presented in four major forms: Do, Consider, Avoid, and Do not. These directives help focus attention on practices that should always be used, those that should generally be used, those that should rarely be used, and those that should never be used. Every guideline includes a discussion of its applicability, and most include a code example to help illuminate the dialogue. Framework Design Guidelines, Second Edition, is the only definitive source of best practices for managed code API development, direct from the architects themselves. 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 and tools are also included.
show more

Product details

  • Mixed media product | 480 pages
  • 177.8 x 238.76 x 33.02mm | 952.54g
  • Addison-Wesley Educational Publishers Inc
  • New Jersey, United States
  • English
  • Revised
  • 2nd edition
  • 0321545613
  • 9780321545619
  • 228,655

About Krzysztof Cwalina

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.
show more

Review quote

"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 teamcreated 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
show more

Table of contents

Figures xviiTables xixForeword xxiForeword to the First Edition xxiiiPreface xxvAcknowledgments xxxiAbout the Authors xxxiiiAbout the Annotators xxxv Chapter 1: Introduction 11.1: Qualities of a Well-Designed Framework 3Chapter 2: Framework Design Fundamentals 92.1: Progressive Frameworks 112.2: Fundamental Principles of Framework Design 14Chapter 3: Naming Guidelines 373.1: Capitalization Conventions 383.2: General Naming Conventions 463.3: Names of Assemblies and DLLs 543.4: Names of Namespaces 563.5: Names of Classes, Structs, and Interfaces 603.6: Names of Type Members 683.7: Naming Parameters 733.8: Naming Resources 74Chapter 4: Type Design Guidelines 774.1: Types and Namespaces 794.2: Choosing Between Class and Struct 844.3: Choosing Between Class and Interface 884.4: Abstract Class Design 954.5: Static Class Design 974.6: Interface Design 984.7: Struct Design 1014.8: Enum Design 1034.9: Nested Types 1154.10: Types and Assembly Metadata 118Chapter 5: Member Design 1215.1: General Member Design Guidelines 1215.2: Property Design 1385.3: Constructor Design 1445.4: Event Design 1535.5: Field Design 1595.6: Extension Methods 1625.7: Operator Overloads 1685.8: Parameter Design 175Chapter 6: Designing for Extensibility 1936.1: Extensibility Mechanisms 1936.2: Base Classes 2066.3: Sealing 207Chapter 7: Exceptions 2117.1: Exception Throwing 2167.2: Choosing the Right Type of Exception to Throw 2217.3: Using Standard Exception Types 2347.4: Designing Custom Exceptions 2397.5: Exceptions and Performance 240Chapter 8: Usage Guidelines 2458.1: Arrays 2458.2: Attributes 2478.3: Collections 2508.4: DateTime and DateTimeOffset 2618.5: ICloneable 2638.6: IComparable and IEquatable 2648.7: IDisposable 2668.8: Nullable 2668.9: Object 2688.10: Serialization 2748.11: Uri 2838.12: System.Xml Usage 2848.13: Equality Operators 286Chapter 9: Common Design Patterns 2899.1: Aggregate Components 2899.2: The Async Patterns 2989.3: Dependency Properties 3129.4: Dispose Pattern 3199.5: Factories 3329.6: LINQ Support 3379.7: Optional Feature Pattern 3449.8: Simulating Covariance 3489.9: Template Method 3549.10: Timeouts 3569.11: XAML Readable Types 3589.12: And in the End... 361AppendixA: C# Coding Style Conventions 363A.1: General Style Conventions 364A.2: Naming Conventions 367A.3: Comments 368A.4: File Organization 369AppendixB: Using FxCop to Enforce the Framework Design Guidelines 371B.1: What Is FxCop? 371B.2: The Evolution of FxCop 372B.3: How Does It Work? 373B.4: FxCop Guideline Coverage 374AppendixC: Sample API Specification 405 Glossary 413Suggested Reading List 419Index 423
show more

Rating details

282 ratings
4.18 out of 5 stars
5 41% (115)
4 43% (121)
3 11% (32)
2 4% (10)
1 1% (4)
Book ratings by Goodreads
Goodreads is the world's largest site for readers with over 50 million reviews. We're featuring millions of their reader ratings on our book pages to help you find your new favourite book. Close X