point
The Smart Techie was renamed Siliconindia India Edition starting Feb 2012 to continue the nearly two decade track record of excellence of our US edition.

Layering Frameworks over Frameworks

Ralph Vaz
Wednesday, January 2, 2008
Ralph Vaz
.NET, as amazing as it is, needs to be understood as a framework rather than a technology. One can build products on .NET or build an extensible framework that defines the product.

Let’s take the scenario of a Content Management Application (CMS). A large part of the solution can be categorized as forms that collect the input and apply Presentation logic to it. This becomes a great starting point for a framework.

Would you now build a forms framework and Presentation framework? No, I guess! You would use ASP Web Forms, Master Pages, and User or Web Controls as your underlying framework and only build sub-class layers specific to your application. You would use .NET Membership and Role provider framework to sort out the authentication and authorization problems.

So what is the outcome here? You have now built a Content Management Framework above the .NET framework. With this you have also given the world of smart developers the ability to use your framework and interact with the .NET Framework to attach their own fancy framework over it. You have also extended your product to the .NET community as the learning curve is now fairly small.

The difficulty of mastering a huge CMS product has now been mitigated by the easily understood ‘how to use’ instructions of the user interface. The framework is still .NET
Your product framework on .NET just feels like the only right thing to do!

Share on Twitter
Share on LinkedIn
Share on facebook