What email address or phone number would you like to use to sign in to Docs.com?
If you already have an account that you use with Office or other Microsoft services, enter it here.
Or sign in with:
Signing in allows you to download and like content, and it provides the authors analytical data about your interactions with their content.
Embed code for: asp_net_mvc_poster
Select a size
Custom handler (IHttpHandler) Incoming HTTP request IIS / ASP.NET Core routing engine (UrlRoutingModule) Matching route entry (in RouteTable.Routes) MVC Framework routing (MvcRouteHandler) Controller factory (DefaultControllerFactory or custom IControllerFactory) Regular controller (Derived from Controller) Your action method Returns action result (ActionResult) View engine Your WebForm view WebForm view rendered No matching file on disk Matching file on disk Served directly Custom route handler (IRouteHandler) Nonstandard controller (IController) Write directly to HTTP response Not a ViewResult ActionResult executed Is a ViewResult Custom view engine (IViewEngine) ASP.NET MVC: The Request-Handling Pipeline Original diagram taken from Pro ASP .NET MVC Framework (Steven Sanderson, Apress) Parses incoming URLs according to your configured routing schema, and then dispatches control to the matching route handler (typically, a controller) Lets you define an arbitrary clean, human-readable, search- engine optimized (SEO) URL structure independently of the code that handles those URLs Render data supplied by the controller as HTML via a templating mechanism Use ASPX templates which support Visual Studio IntelliSense and master pages, or use your own custom view engine Keeps HTML construction simple and separate from other application concerns No sophisticated server-side controls involved, so can be edited by HTML designers who need no knowledge of ASP.NET. No viewstate, no postbacks, and no ID mangling, so works great with jQuery or any other client-side toolkit. PURPOSE: BENEFIT: 1: ROUTING Controllers are collections of “action methods”, each of which is a .NET method that hosts your logic for handling a particular type of request (such as saving a record). An action method may call your model layer to load/save data and to invoke business operations, and then may produce output by rendering a view. PURPOSE: Can use “filters” (not shown on diagram) to tag reusable behaviours before and after authorization, action methods, action results, and unhandled exceptions FEATURE: Can enforce access control by applying an authorization filter to an action method FEATURE: Automatically parses incoming HTTP data into .NET objects (“model binding”) FEATURE: Structured to make application logic simple and testable (e.g., for Test-Driven Development) BENEFIT: 2: CONTROLLERS and ACTIONS 3: VIEWS PURPOSE: FEATURE: FEATURE: BENEFIT: