ASP.NET MVC Request Flow

Posted on 9/27/2008 6:35:34 PM by Justin Etheredge

I gave a presentation Thursday at the Richmond Meet and Code. This presentation covered Microsoft's new web app framework "ASP.NET MVC". My presentation was actually quite short, but one of the things I wanted to show was the flow of a request into System.Web.Routing and through System.Web.MVC. I looked around on the web and I could not find one, so I ended up creating one. I decided to go ahead and reformat it to fit on the blog.

This graphic shows the user sending in a url, and a Route being matched inside of the RouteCollection. I glossed over this part a bit, but what I wanted to highlight was the Url and RouteHandler that the Route class held. This is the way in which the request is passed from System.Web.Routing over to System.Web.Mvc. Once it gets into System.Web.Mvc I tried to show all of the major classes involved and the method that is invoked on each.

I hope that this helps someone out!

Article Info: 11 comments • Share your thoughts; Filed under: Software Development; Tagged: asp.net mvc

Submit This…

DZone This…

Comments

Great talk the other night. Definitely appreciate you putting on the event.

Chris Stewart

September 27. 2008 23:37

Just came across this blog and the request flow diagram is just what was required for me...

Thanks.
Rajesh Pillai

Rajesh Pillai

September 28. 2008 04:59

Pingback from alvinashcraft.com

Dew Drop – September 28, 2008 | Alvin Ashcraft's Morning Dew

alvinashcraft.com

September 28. 2008 05:52

@Chris Thanks! I thought the talk went really well.

@Rajesh Glad it helps out.

Justin Etheredge

September 28. 2008 10:21

Trackback from gOODiDEA.NET

Interesting Finds: 2008.09.29

gOODiDEA.NET

September 28. 2008 19:44

Trackback from gOODiDEA

Interesting Finds: 2008.09.29

gOODiDEA

September 28. 2008 19:44

Pingback from blog.cwa.me.uk

Reflective Perspective - Chris Alcock » The Morning Brew # 189

blog.cwa.me.uk

September 29. 2008 00:11

Trackback from DotNetKicks.com

ASP.NET MVC Request Flow

DotNetKicks.com

September 29. 2008 11:32

This is helpful, but I'm still a little fuzzy on what happens to my ActionResult - how it magically picks a view and renders it. I'd assume Execute() does something with it, but maybe you could add the return path after InvokeAction to the diagram?

Daniel

September 30. 2008 10:14

@Daniel When you just return "View()" from an action it is going to pick a View that has the same name as the action being invoked and within the proper folder for the controller you are in. But you can also specify a view name if you want.

Justin Etheredge

September 30. 2008 13:07