231 Views
ASP.NET MVC has been designed with extensibility as its design principle. In fact, the best way to develop applications with ASP.NET MVC is to extend the system, Simone Chiaretta starts a series that explains how to implement extensions to ASP.NET MVC, covering the entire pipeline. But first, an overview...
3 comments
dpeterson
9/28/2011 8:58:01 AM
I think that most often, when I look to extend someone else's library or product, I find myself scratching my head wondering what the correct way to go about it is. This article starts right where it needs to by explaining where extensions fit into the ASP.NET MVC pipeline. Good read for sure.
vijayst
9/29/2011 9:20:16 AM
The article explains MVC extensibility in detail. The use of flowcharts makes it easy to understand the extensibility points better. A few examples of where we may have to use the extensibility point could make this article complete in all respects. It is definitely a good read. Thanks.
vijayst
9/29/2011 9:21:22 AM
The article explains MVC extensibility in detail. The use of flowcharts makes it easy to understand the extensibility points better. A few examples of where we may have to use the extensibility point could make this article complete in all respects. It is definitely a good read. Thanks.