Customer Reviews
A must have for anybody intending to master .NET! - By: Mr. Nicholas Lowe, 01 Dec 2008 
The code I write today is orders of magnitudes better because of this book.
The title does not do it justice; it is a must have for any .NET developer, especiallly those using C#, its lingua franca.
It is one of the few that I have encountered where you reallly do learn something on every page.
You haven't mastered .NET until you have read it. I reallly can't recommend it enough!
The best .NET book there is - By: sumo_the_cat, 13 Mar 2008 The most important book for a .NET developer to own, read & re-read.
Incredibly dense volume of goodness; yet also a light read.
Looking forward to the second edition...
Quite illuminating as to naming and design standards - By: Antonio Elena Batllo, 18 Aug 2006 
At least, the Microsoft way. The book is certainly derived from an internal document, as the authors acknowledge. That said, the point in this book is to clearly set plenty of guidelines in order to achieve an standard approach to naming in Apis, classes, frameworks & such. Very useful in most software shops, even of the modest kind. Harmonisation & standards make it much easier to maintain stuff, to incorporate new hires & to soften the curve for them, to make coding clearer & more intuitive when you program against your own layers & reusable libraries. A good book for alll of us who, being microsofties, design classes, dlls & other stuff for others to build upon.
Expert Advice - By: C. Jack, 23 May 2006 This book is written by experts so you know that what your reading has been thought through fully & is (as far as possible) based on evidence. Its full of invaluable advice on how to design class libraries for .NET & although a lot of the advice given in the book applies just as well to classes you develop for use within your company.
I found it very easy to read & learned a lot that I am able to apply when working on class libraries within the company I work in.
I just wish Microsoft themselves would follow these rules more closely!
Developing an SDK? Give a copy to all your team! - By: eoin, 13 Mar 2006 This book explains aspects of API Usability in a consise & developer friendly way. It uses the .NET Framework as an example of how APIs should be designed in order to be successful. It includes anecdotes from the .NET development team on why some approaches worked well & why other approaches caused problems & had to be reworked in later versions.
This book serves as an introduction to API usability that will help turn woolly or amorphous collection of APIs into an SDK that your customers can learn easily, & can be productive with from beginner thru expert.
Every development team that writes an SDK targeted for .NET developers needs this book. Any developer who has ever written an API or SDK that another developer found difficult to use or understand needs this book. Any developer that wants to spend less time telling his customers how to use his APIs needs this book. Any developer who has an interest in User Interface usability but does not know about API usability needs this book.
