10 routing
Upcoming SlideShare
Loading in...5

10 routing






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

10 routing 10 routing Presentation Transcript

  • Routing inASP.NET MVC
  • Remember, browsers makeHTTP requests
  • HTTP requests use a verb tocommunicate their intent› GET› POST› PUT› DELETE View slide
  • Alright. Got that out of the way. Now back to our regularly- scheduled lecture.›  asdf View slide
  • Which is better?This …http://www.tic.com/Report.aspx?Type=Sales&year=2012&month=07!… or this …http://www.tic.com/Sales/2012/7! Why?
  • Reasons›  SEO›  Easy to type›  Easy to remember›  Hides implementation stack›  URLs don’t have to change when the site changes.›  Hackable
  • URLs point to resources.›  Uniform ________________ locator›  They don’t point to pages›  So RESTful URLs are more accurate, actually
  • REST is …›  an architectural style …›  for addressing resources …›  in a stateless environment …›  that reduces coupling
  • A RESTful URL is one thatconforms to all of the constraints›  Separation between client and server›  Stateless communication›  Cacheable›  A layered system›  A uniform interface
  • A layered system has predictableparts The usual method Properly RESTful url Category Category Thing Thing Action ID ID (Use HTTP method as action)
  • Use the HTTP requests to specifythe action› GET› POST› PUT› DELETE
  • The URL should act as an API› http://tic.com/Associate/List› http://tic.com/Associate/Create› http://tic.com/Associate/Details/71› http://tic.com/Associate/Edit/71› http://tic.com/Associate/Delete/71› http://tic.com/Department› http://tic.com/Customer› http://tic.com/AddToCart/17
  • There are certain things youcan do to make a URL RESTful›  Give every “thing” an ID›  Link things together›  Use standard methods›  Resources with multiple representations›  Communicate statelessly
  • Give every thing an ID ›  Easy to do if youre using a primary key and a database behind it
  • Link things together›  Also easy to do if youre using HTML
  • Use standard methods
  • Resources with multiple representations› HTML› XML› VCard
  • Communicate statelessly›  Aaaand yet again, the web makes this easy.
  • Okay, Im sold on RESTful urls.How do I get them intoMVC?
  • Registeringroutes tellsIIS that if auser asksfor X, sendthem to Y
  • We use the MapRoute()method to create these routesMyRoutes.MapRoute(! string RouteName,! string URL,! object Defaults);!›  Says when URL comes through, what do we do with it?
  • Routing in ASP.NET MVC areset in Application_Start›  Pulled out into a static method by default.public static void RegisterRoutes(RouteCollection routes)!{! routes.IgnoreRoute("{resource}.axd/{*pathInfo}");! routes.MapRoute(! "Default", // Route name! "{controller}/{action}/{id}", // URL with parms! new { controller = "Home", action = "Index", ! id = UrlParameter.Optional } // defaults! );!}!
  • Routes are matched in orderthat they appear
  • These routes work for WebFormsalso›  Theyre exactly the same.
  • Hardcoded routes are easyroutes.MapRoute(! "ListAllProducts",! "Product/List",! "~/Admin/Products.aspx?id=all",! false! );!
  • Hands-on literal routes
  • We put placeholders in curlybraces›  aka. URL Parameters
  • ExamplesRoute definition Example of matching url{controller}/{action}/ /Products/show/beverage{category}{table}/details.aspx /Products/Details.aspxblog/{action}/{entry} blog/read/1234{reportType}/{year}/{month}/ /sales/2012/7/15{day}{locale}/{action} en-US/show
  • Hands-on matching routes
  • Optional parameters can saveyou from creating a lot ofroutes›  Example: you want to match›  Clients/Miller›  Clients/Miller/Harold›  Clients/Miller/Harold/Dr›  … with the same route›  Simply make first name and title optional with:›  new { FirstName = UrlParameter.Optional, Title = UrlParameter.Optional }
  • Hands-on optional parameters
  • Hands-on default values
  • The parameters can have oneof two types of constraints1.  Regular expressions2.  An IRouteConstraint
  • Regular expression constraintsroutes.MapRoute(! "BlogArchive",! "Archive/{entryDate}",! new { controller="Blog", action="Archive" }, ! new { entryDate=@"d{2}-d{2}-d{4}" }!);!
  • Hands-on constraints
  • Conclusion›  RESTful urls are easier to use, therefore better›  MVC lends itself well to REST; in fact REST is pretty much required to get to controllers and actions›  Routes are set up in the global.asax file
  • Further study›  Intro to REST ›  http://www.infoq.com/articles/rest- introduction