一、命名參數規範+匿名對象
1 routes.MapRoute(name: "Default", 2 url: "{controller}/{action}/{id}", 3 defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional } );
構造路由然後添加
1 Route myRoute = new Route("{controller}/{action}", new MvcRouteHandler()); 2 routes.Add("MyRoute", myRoute);
二、直接方法重載+匿名對象
1 routes.MapRoute("ShopSchema", "Shop/{action}", new { controller = "Home" });
個人覺得第一種比較易懂，第二種方便調試，第三種寫起來比較效率吧。各取所需吧。本文行文偏向於第三種。
1.默認路由(MVC自帶)
1 routes.MapRoute( 2 "Default", // 路由名稱 3 "{controller}/{action}/{id}", // 帶有參數的 URL 4 new { controller = "Home", action = "Index", id = UrlParameter.Optional } // 參數默認值
2.靜態URL段
1 routes.MapRoute("ShopSchema2", "Shop/OldAction", new { controller = "Home", action = "Index" }); 2 routes.MapRoute("ShopSchema", "Shop/{action}", new { controller = "Home" }); 3 routes.MapRoute("ShopSchema2", "Shop/OldAction.js", 4 new { controller = "Home", action = "Index" });
沒有佔位符路由就是現成的寫死的。
比如這樣寫然後去訪問http://localhost:XXX/Shop/OldAction.js，response也是完全沒問題的。 controller , action , area這三個保留字就別設靜態變量裏面了。
3.自定義常規變量URL段
1 routes.MapRoute("MyRoute2", "{controller}/{action}/{id}", new { controller = "Home", action = "Index", id = "DefaultId" });
這種情況如果訪問 /Home/Index 的話，因爲第三段(id)沒有值，根據路由規則這個參數會被設爲DefaultId
這個用viewbag給title賦值就能很明顯看出
1 ViewBag.Title = RouteData.Values["id"];
結果是標題顯示爲DefaultId， 注意要在控制器裏面賦值，在視圖賦值沒法編譯的。
4.再述默認路由
然後再回到默認路由。 UrlParameter.Optional這個叫可選URL段.路由裏沒有這個參數的話id爲null。 照原文大致說法，這個可選URL段能用來實現一個關注點的分離。剛纔在路由裏直接設定參數默認值其實不是很好。照我的理解，實際參數是用戶發來的，我們做的只是定義形式參數名。但是，如果硬要給參數賦默認值的話，建議用語法糖寫到action參數裏面。比如：
public ActionResult Index(string id = "abcd") { ViewBag.Title = RouteData.Values["id"]; return View(); }
5.可變長度路由
routes.MapRoute("MyRoute", "{controller}/{action}/{id}/{*catchall}", new { controller = "Home", action = "Index", id = UrlParameter.Optional });
在這裏id和最後一段都是可變的，所以 /Home/Index/dabdafdaf 等效於 /Home/Index//abcdefdjldfiaeahfoeiho 等效於 /Home/Index/All/Delete/Perm/.....
6.跨命名空間路由
這個提醒一下記得引用命名空間，開啓IIS網站不然就是404。這個非常非主流，不建議瞎搞。
routes.MapRoute("MyRoute", "{controller}/{action}/{id}/{*catchall}", new { controller = "Home", action = "Index", id = UrlParameter.Optional }, new[] { "URLsAndRoutes.AdditionalControllers", "UrlsAndRoutes.Controllers" });
但是這樣寫的話數組排名不分先後的，如果有多個匹配的路由會報錯。 然後作者提出了一種改進寫法。
routes.MapRoute("AddContollerRoute", "Home/{action}/{id}/{*catchall}", new { controller = "Home", action = "Index", id = UrlParameter.Optional }, new[] { "URLsAndRoutes.AdditionalControllers" }); routes.MapRoute("MyRoute", "{controller}/{action}/{id}/{*catchall}", new { controller = "Home", action = "Index", id = UrlParameter.Optional }, new[] { "URLsAndRoutes.Controllers" });
這樣第一個URL段不是Home的都交給第二個處理 最後還可以設定這個路由找不到的話就不給後面的路由留後路啦，也就不再往下找啦。
1 Route myRoute = routes.MapRoute("AddContollerRoute", 2 "Home/{action}/{id}/{*catchall}", 3 new { controller = "Home", action = "Index", id = UrlParameter.Optional }, 4 new[] { "URLsAndRoutes.AdditionalControllers" }); myRoute.DataTokens["UseNamespaceFallback"] = false;
7.正則表達式匹配路由
1 routes.MapRoute("MyRoute", 2 "{controller}/{action}/{id}/{*catchall}", 3 new { controller = "Home", action = "Index", id = UrlParameter.Optional }, 4 new { controller = "^H.*"}, 5 new[] { "URLsAndRoutes.Controllers"});
約束多個URL
routes.MapRoute("MyRoute", "{controller}/{action}/{id}/{*catchall}", new { controller = "Home", action = "Index", id = UrlParameter.Optional }, new { controller = "^H.*", action = "^Index$|^About___FCKpd___13quot;}, new[] { "URLsAndRoutes.Controllers"});
8.指定請求方法
1 routes.MapRoute("MyRoute", "{controller}/{action}/{id}/{*catchall}", 2 new { controller = "Home", action = "Index", id = UrlParameter.Optional }, 3 new { controller = "^H.*", action = "Index|About", httpMethod = new HttpMethodConstraint("GET") }, 4 new[] { "URLsAndRoutes.Controllers" });
9.最後還是不爽的話自己寫個類實現 IRouteConstraint的匹配方法。
1 using System; 2 using System.Collections.Generic; 3 using System.Linq; 4 using System.Web; 5 using System.Web.Routing; 6 /// <summary> 7 /// If the standard constraints are not sufficient for your needs, you can define your own custom constraints by implementing the IRouteConstraint interface. 8 /// </summary> 9 public class UserAgentConstraint : IRouteConstraint 10 { 11 12 private string requiredUserAgent; 13 public UserAgentConstraint(string agentParam) 14 { 15 requiredUserAgent = agentParam; 16 } 17 public bool Match(HttpContextBase httpContext, Route route, string parameterName, 18 RouteValueDictionary values, RouteDirection routeDirection) 19 { 20 return httpContext.Request.UserAgent != null && 21 httpContext.Request.UserAgent.Contains(requiredUserAgent); 22 } 23 }
1 routes.MapRoute("ChromeRoute", "{*catchall}", 2 3 new { controller = "Home", action = "Index" }, 4 5 new { customConstraint = new UserAgentConstraint("Chrome") }, 6 7 new[] { "UrlsAndRoutes.AdditionalControllers" });
比如這個就用來匹配是否是用谷歌瀏覽器訪問網頁的。
10.訪問本地文檔
1 routes.RouteExistingFiles = true; 2 3 routes.MapRoute("DiskFile", "Content/StaticContent.html", new { controller = "Customer", action = "List", });
瀏覽網站，以開啓 IIS Express，然後點顯示所有應用程序-點擊網站名稱-配置(applicationhost.config)-搜索UrlRoutingModule節點
1 <add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="managedHandler,runtimeVersionv4.0" />
把這個節點裏的preCondition刪除，變成
1 <add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="" />
11.直接訪問本地資源，繞過了路由系統
1 routes.IgnoreRoute("Content/{filename}.html");
文件名還可以用 {filename}佔位符。
IgnoreRoute方法是RouteCollection裏面StopRoutingHandler類的一個實例。路由系統通過硬-編碼識別這個Handler。如果這個規則匹配的話，後面的規則都無效了。 這也就是默認的路由裏面routes.IgnoreRoute("{resource}.axd/{*pathInfo}");寫最前面的原因。
三、路由測試(在測試項目的基礎上，要裝moq)
1 PM> Install-Package Moq
1 using System; 2 using Microsoft.VisualStudio.TestTools.UnitTesting; 3 using System.Web; 4 using Moq; 5 using System.Web.Routing; 6 using System.Reflection; 7 [TestClass] 8 public class RoutesTest 9 { 10 private HttpContextBase CreateHttpContext(string targetUrl = null, string HttpMethod = "GET") 11 { 12 // create the mock request 13 Mock<HttpRequestBase> mockRequest = new Mock<HttpRequestBase>(); 14 mockRequest.Setup(m => m.AppRelativeCurrentExecutionFilePath) 15 .Returns(targetUrl); 16 mockRequest.Setup(m => m.HttpMethod).Returns(HttpMethod); 17 // create the mock response 18 Mock<HttpResponseBase> mockResponse = new Mock<HttpResponseBase>(); 19 mockResponse.Setup(m => m.ApplyAppPathModifier( 20 It.IsAny<string>())).Returns<string>(s => s); 21 // create the mock context, using the request and response 22 Mock<HttpContextBase> mockContext = new Mock<HttpContextBase>(); 23 mockContext.Setup(m => m.Request).Returns(mockRequest.Object); 24 mockContext.Setup(m => m.Response).Returns(mockResponse.Object); 25 // return the mocked context 26 return mockContext.Object; 27 } 28 29 private void TestRouteMatch(string url, string controller, string action, object routeProperties = null, string httpMethod = "GET") 30 { 31 // Arrange 32 RouteCollection routes = new RouteCollection(); 33 RouteConfig.RegisterRoutes(routes); 34 // Act - process the route 35 RouteData result = routes.GetRouteData(CreateHttpContext(url, httpMethod)); 36 // Assert 37 Assert.IsNotNull(result); 38 Assert.IsTrue(TestIncomingRouteResult(result, controller, action, routeProperties)); 39 } 40 41 private bool TestIncomingRouteResult(RouteData routeResult, string controller, string action, object propertySet = null) 42 { 43 Func<object, object, bool> valCompare = (v1, v2) => 44 { 45 return StringComparer.InvariantCultureIgnoreCase 46 .Compare(v1, v2) == 0; 47 }; 48 bool result = valCompare(routeResult.Values["controller"], controller) 49 && valCompare(routeResult.Values["action"], action); 50 if (propertySet != null) 51 { 52 PropertyInfo[] propInfo = propertySet.GetType().GetProperties(); 53 foreach (PropertyInfo pi in propInfo) 54 { 55 if (!(routeResult.Values.ContainsKey(pi.Name) 56 && valCompare(routeResult.Values[pi.Name], 57 pi.GetValue(propertySet, null)))) 58 { 59 result = false; 60 break; 61 } 62 } 63 } 64 return result; 65 } 66 67 private void TestRouteFail(string url) 68 { 69 // Arrange 70 RouteCollection routes = new RouteCollection(); 71 RouteConfig.RegisterRoutes(routes); 72 // Act - process the route 73 RouteData result = routes.GetRouteData(CreateHttpContext(url)); 74 // Assert 75 Assert.IsTrue(result == null || result.Route == null); 76 } 77 78 [TestMethod] 79 public void TestIncomingRoutes() 80 { 81 // check for the URL that we hope to receive 82 TestRouteMatch("~/Admin/Index", "Admin", "Index"); 83 // check that the values are being obtained from the segments 84 TestRouteMatch("~/One/Two", "One", "Two"); 85 // ensure that too many or too few segments fails to match 86 TestRouteFail("~/Admin/Index/Segment");//失敗 87 TestRouteFail("~/Admin");//失敗 88 TestRouteMatch("~/", "Home", "Index"); 89 TestRouteMatch("~/Customer", "Customer", "Index"); 90 TestRouteMatch("~/Customer/List", "Customer", "List"); 91 TestRouteFail("~/Customer/List/All");//失敗 92 TestRouteMatch("~/Customer/List/All", "Customer", "List", new { id = "All" }); 93 TestRouteMatch("~/Customer/List/All/Delete", "Customer", "List", new { id = "All", catchall = "Delete" }); 94 TestRouteMatch("~/Customer/List/All/Delete/Perm", "Customer", "List", new { id = "All", catchall = "Delete/Perm" }); 95 } 96 97 98 99 }