website statistics Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries - PDF Books Online
Hot Best Seller

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

Availability: Ready to download

"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 "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 learn The 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 patterns Guidelines 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.


Compare

"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 "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 learn The 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 patterns Guidelines 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.

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

  1. 5 out of 5

    David

    This book has a lot of good advice about designing .NET APIs that everyone from Mort to Jon Skeet can use. This book has a lot of good advice about designing .NET APIs that everyone from Mort to Jon Skeet can use.

  2. 5 out of 5

    Paweł

    Polecam. Podczas czytania napisałem 3 strony A4 notatek. Niektóre rozdziały do ponownego przeczytania, bo tak dobre.

  3. 4 out of 5

    Roger

    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 guideli 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.

  4. 5 out of 5

    Meg

    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 ap 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.

  5. 5 out of 5

    Robert

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

  6. 5 out of 5

    Günter Zöchbauer

    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.

  7. 5 out of 5

    Dwight Walker

    Looks like a useful book for software reuse.

  8. 5 out of 5

    Rabashani

    Your new BIBLE... this is a must for all developers out there!

  9. 5 out of 5

    James Igoe

    Excellent material, a broad view for building for external clients...

  10. 4 out of 5

    Jeff

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

  11. 4 out of 5

    Matthew

    The difference between C# and good C#

  12. 4 out of 5

    Igor Moiseev

    I think this book should read each developer who wants to write reusable assemblies. There are many great advices about right code and styles.

  13. 5 out of 5

    Harshdeep

    Wish I would have read it a decade back, when I started my career. :)

  14. 4 out of 5

    Jerry

  15. 5 out of 5

    Jason

  16. 5 out of 5

    Marcelo

  17. 5 out of 5

    Welshofer

  18. 4 out of 5

    Max

  19. 5 out of 5

    Dennis Rongo

  20. 5 out of 5

    Rob

  21. 5 out of 5

    Michael Terry

  22. 5 out of 5

    Lad

  23. 5 out of 5

    Pete Chen

  24. 4 out of 5

    Gishu Pillai

  25. 4 out of 5

    Rodger Brennan

  26. 4 out of 5

    Waldemar Mękal

  27. 4 out of 5

    Kassem

  28. 5 out of 5

    Dave Thomas

  29. 4 out of 5

    Margaret Mullins

  30. 5 out of 5

    Eizo Nishime

Add a review

Your email address will not be published. Required fields are marked *

Loading...
We use cookies to give you the best online experience. By using our website you agree to our use of cookies in accordance with our cookie policy.