This thread is for discussions of Building Application Framework with C#.

A very good article and written in a very good understandable form.
Frameworks are rightly easing the amount of effort required to put in to code development by developers.
Frameworks provide set of services , but dot NET goes beyond that by managing the code that uses those services. So, dotNET can be viewed as playing dual role (Provision of services and managment of code).

Horrible!!

I thought this was an article about Frameworks??? Instead I get a brief on the basics of Inheritence. A Framework is a much larger issue, and cannot be covered in three HTML pages.

The title gives an impression that we are going to delve deep into application frameworks...but the article is just basic, although its OK.  Better change the title to avoid such comments.

Developing Java for a few years and understanding most of the concepts and theory of the language this tutorial gave me a better idea as to what to expect when making the jump to C#.  Although not in-dept, intricate enough to get the 'just' of the language and framework building.  EXCELLENT JOB!!!!!!!

None serious actual framework uses inheritance or templating. Inversion of Control (aka Dependency Injection Pattern) is a much better design and seems to be the way most popular frameworks had taken.