DevBlog

For the past few months I have been tasked with learning .Net, researching frameworks, and a whole lot more related to .Net. In those few months, read lots of books (in fact, I'm still reading). This entry is the first of several book reviews coming in the next few days.

We struggled with the build vs. buy arguement in regards to a framework and in the ended decided to build. So, I pulled down a book I've had on my shelf for sometime, Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries.

This is a book that is full of great advice on how to design a framework. Think of it as coding and design standards. However, it really is a book that belongs on the shelf of every .Net developer as it gives insight into how the .Net Framework was designed, why things are named like they are, and how you should name things in your own application.

It covers the normal stuff you would expect in a coding standard. Things like naming conventions and usage guidelines, but goes further to talk about when to use standard exceptions or custom exceptions, which datatypes to use when, how common design patterns were applied in the .Net Framework, and much more.

If you're doing any .Net development, get this book. It has place on my shelf within easy reach from keyboard.