ASP.NET MVC Pipeline And Extensibility

| by Roopesh Shenoy Follow 0 Followers on Sep 27, 2011. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

ASP.NET MVC is designed with extensibility in mind and almost every part of processing pipeline is extensible using your own providers to replace the standard implementation. Simone Chiaretta, in his blog post “An Introduction to ASP.NET MVC Extensibility” gives an introduction to various stages in the ASP.NET MVC Pipeline, and a brief explanation of how extensibility comes into picture.

The ASP.NET MVC Pipeline can be divided into the following parts -

  • Routing Part – Routing module tries to match the incoming URL with the routing table, and calling the corresponding IRouteHandler.
  • Controller creation – the IControllerFactory creates an instance of the controller based on route parameters and default naming conventions.
  • Action Execution – the IActionInvoker identifies the method to be executed, the IModelBinder validates and binds the method parameters and the IFilterProvider discovers filters to be applied. The Action returns a type ActionResult.
  • View – the IViewEngine instantiates the correct view engine and the model is passed to the view. Using Model Validation Provider, the validation rules are retrieved to create client-side validation scripts as well as remote validation scripts

Every interface in the above pipeline can be implemented as a custom provider to replace the default implementation, using extensibility. Simone explains the different types of extensions, based on their purpose, and promises to cover each of these in more detail in subsequent articles -

Do checkout the article for a much more detailed explanation.

ASP.NET MVC (Model-View-Controller) is a patterns based way to build dynamic websites in ASP.NET, as an alternative to the event-driven web-forms. It helps in clear separation of concerns and gives full control over the html markup.  

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you