Thursday, May 01, 2008

class recommended over interface

I just pulled the Framework Design Guidelines down from the bookshelf to look at it again. I briefly browsed through it and I must say that disagree with it all the same places as last time I read it. At one point they recommend the use of abstract classes over use of interfaces when making a framework. The reason would be that it's easier to add new methods to the framework later without breaking code build on the framework.

I recommend interfaces over classes when designing a framework. Interfaces give fewer dependencies if you have the choice. Like everything else its dependent on the situation what to do.

The book states what you should do and what you should not. Framework design to me is not so black and white. The book is probably more a description of what practices the .net team followed while designing the .net framework. The book is good for developers with little experience, but it seems a little trivial for experienced developers.


  1. The book is really the thoughts that MS did when they implemented the .NET framework.

    Some of the stuff is somewhat black and white as you state.

    If you want a really cool book on application frameworks in .NET, I can recommend The author Xin Chen discusses frameworks in general before implementing his own. Really great stuff in there...

  2. Cool.. I might look at that some day. As always the problem is lots of interesting things to look into and little time to do it ;)