Documente Academic
Documente Profesional
Documente Cultură
IIS / ASP.NET
Matching file
on disk Core routing engine 1: ROUTING
(UrlRoutingModule) PURPOSE:
Parses incoming URLs according to your configured routing
Served directly schema, and then dispatches control to the matching route
No matching file on disk handler (typically, a controller)
BENEFIT:
Custom route handler Lets you define an arbitrary clean, human-readable, search-
(IRouteHandler)
Matching route entry engine optimized (SEO) URL structure independently of the code
(in RouteTable.Routes) that handles those URLs
Custom handler
(IHttpHandler)
BENEFIT:
Not a ViewResult
Returns action result Structured to make application logic simple and testable
(ActionResult) (e.g., for Test-Driven Development)
ActionResult
executed
Is a ViewResult
3: VIEWS
View engine PURPOSE:
Render data supplied by the controller as HTML via a templating
Custom view engine mechanism
(IViewEngine) FEATURE:
Use ASPX templates which support Visual Studio IntelliSense
and master pages, or use your own custom view engine
Y our WebF orm view
FEATURE:
Keeps HTML construction simple and separate from other
application concerns
BENEFIT:
WebForm view rendered 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.