If it is on Amazon it must be for real 😉
How should we refer to this one? We affectionately call the others SLAR1 and SLAR2… what should this be? I am found of just saying “DG”.. “FDGCIPRNL” seems like a mouth full… Maybe just FDG? Love to have your thoughts on this important issue! 😉
I understand you can pre-order right now… be the first kid on the your block to have one 😉
Here is a descriptive TOC for your enjoyment…
Chapter 1 is a brief introduction to the book describing the general philosophy of framework design, and the only chapter without guidelines.
Chapter 2, Library Design Fundamentals, offers principles and guidelines that are fundamental to overall framework design.
Chapter 3, Naming Guidelines, contains naming guidelines for various parts of a framework, such as namespaces, types, members, common design idioms.
Chapter 4, Type Design, provides guidelines for the general design of types.
Chapter 5, Member Design, takes it a step further and presents guidelines for the design of members of types.
Chapter 6, Designing for Extensibility, presents issues and guidelines that are important to ensure appropriate extensibility in your Framework.
Chapter 7, Exceptions, presents guidelines for working with exceptions, the preferred error reporting mechanisms.
Chapter 8, Usage Guidelines, contains guidelines for extending and using types that commonly appear in frameworks.
Chapter 9, Common Design Patterns, offers guidelines and examples of common framework design patterns.
Appendix A contains a short description of coding conventions used in this book.
Appendix B describes a tool called FxCop. The tool can be used to analyze framework binaries for compliance with the guidelines described in this book. The tool is included on the companion DVD.
Appendix C is an example of an API specification that framework designers within Microsoft create when designing APIs.
Included with the book is a DVD that contains useful resources.