ASP.NETMVC路由配置的示例分析
這篇文章將為大家詳細(xì)講解有關(guān)ASP.NET MVC路由配置的示例分析，小編覺得挺實(shí)用的，因此分享給大家做個參考，希望大家閱讀完這篇文章后可以有所收獲。
創(chuàng)新互聯(lián)建站是一家專業(yè)從事成都網(wǎng)站設(shè)計、網(wǎng)站制作、外貿(mào)營銷網(wǎng)站建設(shè)、網(wǎng)頁設(shè)計的品牌網(wǎng)絡(luò)公司。如今是成都地區(qū)具影響力的網(wǎng)站設(shè)計公司,作為專業(yè)的成都網(wǎng)站建設(shè)公司,創(chuàng)新互聯(lián)建站依托強(qiáng)大的技術(shù)實(shí)力、以及多年的網(wǎng)站運(yùn)營經(jīng)驗(yàn),為您提供專業(yè)的成都網(wǎng)站建設(shè)、營銷型網(wǎng)站建設(shè)及網(wǎng)站設(shè)計開發(fā)服務(wù)！
先說一下基本的路由規(guī)則原則?；镜穆酚梢?guī)則是從特殊到一般排列，也就是最特殊（非主流）的規(guī)則在最前面，最一般（萬金油）的規(guī)則排在最后。這是因?yàn)槠ヅ渎酚梢?guī)則也是照著這個順序的。如果寫反了，那么即便你路由規(guī)則寫對了那照樣坐等404.
XD 首先說URL的構(gòu)造。 其實(shí)這個也談不上構(gòu)造，只是語法特性吧。
URL構(gòu)造
命名參數(shù)規(guī)范+匿名對象
routes.MapRoute(name: "Default",url: "{controller}/{action}/{id}", defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional } );構(gòu)造路由然后添加
Route myRoute = new Route("{controller}/{action}", new MvcRouteHandler());
routes.Add("MyRoute", myRoute);直接方法重載+匿名對象
routes.MapRoute("ShopSchema", "Shop/{action}", new { controller = "Home" });個人覺得第一種比較易懂，第二種方便調(diào)試，第三種寫起來比較效率吧。各取所需吧。本文行文偏向于第三種。
路由規(guī)則
1.默認(rèn)路由(MVC自帶)
routes.MapRoute(
"Default", // 路由名稱
"{controller}/{action}/{id}", // 帶有參數(shù)的 URL
new { controller = "Home", action = "Index", id = UrlParameter.Optional } // 參數(shù)默認(rèn)值 (UrlParameter.Optional-可選的意思) );2.靜態(tài)URL段
routes.MapRoute("ShopSchema2", "Shop/OldAction", new { controller = "Home", action = "Index" });
routes.MapRoute("ShopSchema", "Shop/{action}", new { controller = "Home" });
routes.MapRoute("ShopSchema2", "Shop/OldAction.js",
new { controller = "Home", action = "Index" });沒有占位符路由就是現(xiàn)成的寫死的。
比如這樣寫然后去訪問http://localhost:XXX/Shop/OldAction.js，response也是完全沒問題的。 controller , action , area這三個保留字就別設(shè)靜態(tài)變量里面了。
3.自定義常規(guī)變量URL段（好吧這翻譯暴露智商了）
routes.MapRoute("MyRoute2", "{controller}/{action}/{id}", new { controller = "Home", action = "Index", id = "DefaultId" });這種情況如果訪問 /Home/Index 的話，因?yàn)榈谌危╥d）沒有值，根據(jù)路由規(guī)則這個參數(shù)會被設(shè)為DefaultId
這個用viewbag給title賦值就能很明顯看出
ViewBag.Title = RouteData.Values["id"];
圖不貼了，結(jié)果是標(biāo)題顯示為DefaultId。 注意要在控制器里面賦值，在視圖賦值沒法編譯的。
4.再述默認(rèn)路由
然后再回到默認(rèn)路由。 UrlParameter.Optional這個叫可選URL段.路由里沒有這個參數(shù)的話id為null。 照原文大致說法，這個可選URL段能用來實(shí)現(xiàn)一個關(guān)注點(diǎn)的分離。剛才在路由里直接設(shè)定參數(shù)默認(rèn)值其實(shí)不是很好。照我的理解，實(shí)際參數(shù)是用戶發(fā)來的，我們做的只是定義形式參數(shù)名。但是，如果硬要給參數(shù)賦默認(rèn)值的話，建議用語法糖寫到action參數(shù)里面。比如：
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網(wǎng)站不然就是404。這個非常非主流，不建議瞎搞。
routes.MapRoute("MyRoute","{controller}/{action}/{id}/{*catchall}", new { controller = "Home", action = "Index", id = UrlParameter.Optional },new[] { "URLsAndRoutes.AdditionalControllers", "UrlsAndRoutes.Controllers" });但是這樣寫的話數(shù)組排名不分先后的，如果有多個匹配的路由會報錯。 然后作者提出了一種改進(jìn)寫法。
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的都交給第二個處理 最后還可以設(shè)定這個路由找不到的話就不給后面的路由留后路啦，也就不再往下找啦。
Route myRoute = routes.MapRoute("AddContollerRoute",
"Home/{action}/{id}/{*catchall}",
new { controller = "Home", action = "Index", id = UrlParameter.Optional },
new[] { "URLsAndRoutes.AdditionalControllers" }); myRoute.DataTokens["UseNamespaceFallback"] = false;7.正則表達(dá)式匹配路由
routes.MapRoute("MyRoute", "{controller}/{action}/{id}/{*catchall}",
new { controller = "Home", action = "Index", id = UrlParameter.Optional },
new { controller = "^H.*"},
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$"},
new[] { "URLsAndRoutes.Controllers"});8.指定請求方法
routes.MapRoute("MyRoute", "{controller}/{action}/{id}/{*catchall}",
new { controller = "Home", action = "Index", id = UrlParameter.Optional },
new { controller = "^H.*", action = "Index|About", httpMethod = new HttpMethodConstraint("GET") },
new[] { "URLsAndRoutes.Controllers" });9. WebForm支持
routes.MapPageRoute("", "", "~/Default.aspx");
routes.MapPageRoute("list", "Items/{action}", "~/Items/list.aspx", false, new RouteValueDictionary { { "action", "all" } });
routes.MapPageRoute("show", "Show/{action}", "~/show.aspx", false, new RouteValueDictionary { { "action", "all" } });
routes.MapPageRoute("edit", "Edit/{id}", "~/edit.aspx", false, new RouteValueDictionary { { "id", "1" } }, new RouteValueDictionary { { "id", @"\d+" } });具體的可以看
使用Asp.Net4新特性路由創(chuàng)建WebForm應(yīng)用
或者官方msdn
10.MVC5的RouteAttribute
首先要在路由注冊方法那里
//啟用路由特性映射 routes.MapMvcAttributeRoutes();
這樣
[Route("Login")]route特性才有效.該特性有好幾個重載.還有路由約束啊,順序啊,路由名之類的.
其他的還有路由前綴,路由默認(rèn)值
[RoutePrefix("reviews")]<br>[Route("{action=index}")]<br>public class ReviewsController : Controller<br>{<br>}路由構(gòu)造
// eg: /users/5
[Route("users/{id:int}"]
public ActionResult GetUserById(int id) { ... }
// eg: users/ken
[Route("users/{name}"]
public ActionResult GetUserByName(string name) { ... }參數(shù)限制
// eg: /users/5
// but not /users/10000000000 because it is larger than int.MaxValue,
// and not /users/0 because of the min(1) constraint.
[Route("users/{id:int:min(1)}")]
public ActionResult GetUserById(int id) { ... }| Constraint | Description | Example |
|---|---|---|
| alpha | Matches uppercase or lowercase Latin alphabet characters (a-z, A-Z) | {x:alpha} |
| bool | Matches a Boolean value. | {x:bool} |
| datetime | Matches a DateTime value. | {x:datetime} |
| decimal | Matches a decimal value. | {x:decimal} |
| double | Matches a 64-bit floating-point value. | {x:double} |
| float | Matches a 32-bit floating-point value. | {x:float} |
| guid | Matches a GUID value. | {x:guid} |
| int | Matches a 32-bit integer value. | {x:int} |
| length | Matches a string with the specified length or within a specified range of lengths. | {x:length(6)} {x:length(1,20)} |
| long | Matches a 64-bit integer value. | {x:long} |
| max | Matches an integer with a maximum value. | {x:max(10)} |
| maxlength | Matches a string with a maximum length. | {x:maxlength(10)} |
| min | Matches an integer with a minimum value. | {x:min(10)} |
| minlength | Matches a string with a minimum length. | {x:minlength(10)} |
| range | Matches an integer within a range of values. | {x:range(10,50)} |
| regex | Matches a regular expression. | {x:regex(^\d{3}-\d{3}-\d{4}$)} |
具體的可以參考
Attribute Routing in ASP.NET MVC 5
對我來說,這樣的好處是分散了路由規(guī)則的定義.有人喜歡集中,我個人比較喜歡這種靈活的處理.因?yàn)檫@個action定義好后,我不需要跑到配置那里定義對應(yīng)的路由規(guī)則
11.最后還是不爽的話自己寫個類實(shí)現(xiàn) IRouteConstraint的匹配方法。
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Routing;
/// <summary>
/// If the standard constraints are not sufficient for your needs, you can define your own custom constraints by implementing the IRouteConstraint interface.
/// </summary>
public class UserAgentConstraint : IRouteConstraint
{
private string requiredUserAgent;
public UserAgentConstraint(string agentParam)
{
requiredUserAgent = agentParam;
}
public bool Match(HttpContextBase httpContext, Route route, string parameterName,
RouteValueDictionary values, RouteDirection routeDirection)
{
return httpContext.Request.UserAgent != null &&
httpContext.Request.UserAgent.Contains(requiredUserAgent);
}
}routes.MapRoute("ChromeRoute", "{*catchall}",
new { controller = "Home", action = "Index" },
new { customConstraint = new UserAgentConstraint("Chrome") },
new[] { "UrlsAndRoutes.AdditionalControllers" });比如這個就用來匹配是否是用谷歌瀏覽器訪問網(wǎng)頁的。
12.訪問本地文檔
routes.RouteExistingFiles = true;
routes.MapRoute("DiskFile", "Content/StaticContent.html", new { controller = "Customer", action = "List", });瀏覽網(wǎng)站，以開啟 IIS Express，然后點(diǎn)顯示所有應(yīng)用程序-點(diǎn)擊網(wǎng)站名稱-配置（applicationhost.config）-搜索UrlRoutingModule節(jié)點(diǎn)
<add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="managedHandler,runtimeVersionv4.0" />
把這個節(jié)點(diǎn)里的preCondition刪除，變成
<add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="" />
13.直接訪問本地資源，繞過了路由系統(tǒng)
routes.IgnoreRoute("Content/{filename}.html");文件名還可以用 {filename}占位符。
IgnoreRoute方法是RouteCollection里面StopRoutingHandler類的一個實(shí)例。路由系統(tǒng)通過硬-編碼識別這個Handler。如果這個規(guī)則匹配的話，后面的規(guī)則都無效了。 這也就是默認(rèn)的路由里面routes.IgnoreRoute("{resource}.axd/{*pathInfo}");寫最前面的原因。
路由測試（在測試項(xiàng)目的基礎(chǔ)上，要裝moq）
PM> Install-Package Moq
using System;
using Microsoft.VisualStudio.TestTools.UnitTesting;
using System.Web;
using Moq;
using System.Web.Routing;
using System.Reflection;
[TestClass]
public class RoutesTest
{
private HttpContextBase CreateHttpContext(string targetUrl = null, string HttpMethod = "GET")
{
// create the mock request
Mock<HttpRequestBase> mockRequest = new Mock<HttpRequestBase>();
mockRequest.Setup(m => m.AppRelativeCurrentExecutionFilePath)
.Returns(targetUrl);
mockRequest.Setup(m => m.HttpMethod).Returns(HttpMethod);
// create the mock response
Mock<HttpResponseBase> mockResponse = new Mock<HttpResponseBase>();
mockResponse.Setup(m => m.ApplyAppPathModifier(
It.IsAny<string>())).Returns<string>(s => s);
// create the mock context, using the request and response
Mock<HttpContextBase> mockContext = new Mock<HttpContextBase>();
mockContext.Setup(m => m.Request).Returns(mockRequest.Object);
mockContext.Setup(m => m.Response).Returns(mockResponse.Object);
// return the mocked context
return mockContext.Object;
}
private void TestRouteMatch(string url, string controller, string action, object routeProperties = null, string httpMethod = "GET")
{
// Arrange
RouteCollection routes = new RouteCollection();
RouteConfig.RegisterRoutes(routes);
// Act - process the route
RouteData result = routes.GetRouteData(CreateHttpContext(url, httpMethod));
// Assert
Assert.IsNotNull(result);
Assert.IsTrue(TestIncomingRouteResult(result, controller, action, routeProperties));
}
private bool TestIncomingRouteResult(RouteData routeResult, string controller, string action, object propertySet = null)
{
Func<object, object, bool> valCompare = (v1, v2) =>
{
return StringComparer.InvariantCultureIgnoreCase
.Compare(v1, v2) == 0;
};
bool result = valCompare(routeResult.Values["controller"], controller)
&& valCompare(routeResult.Values["action"], action);
if (propertySet != null)
{
PropertyInfo[] propInfo = propertySet.GetType().GetProperties();
foreach (PropertyInfo pi in propInfo)
{
if (!(routeResult.Values.ContainsKey(pi.Name)
&& valCompare(routeResult.Values[pi.Name],
pi.GetValue(propertySet, null))))
{
result = false;
break;
}
}
}
return result;
}
private void TestRouteFail(string url)
{
// Arrange
RouteCollection routes = new RouteCollection();
RouteConfig.RegisterRoutes(routes);
// Act - process the route
RouteData result = routes.GetRouteData(CreateHttpContext(url));
// Assert
Assert.IsTrue(result == null || result.Route == null);
}
[TestMethod]
public void TestIncomingRoutes()
{
// check for the URL that we hope to receive
TestRouteMatch("~/Admin/Index", "Admin", "Index");
// check that the values are being obtained from the segments
TestRouteMatch("~/One/Two", "One", "Two");
// ensure that too many or too few segments fails to match
TestRouteFail("~/Admin/Index/Segment");//失敗
TestRouteFail("~/Admin");//失敗
TestRouteMatch("~/", "Home", "Index");
TestRouteMatch("~/Customer", "Customer", "Index");
TestRouteMatch("~/Customer/List", "Customer", "List");
TestRouteFail("~/Customer/List/All");//失敗
TestRouteMatch("~/Customer/List/All", "Customer", "List", new { id = "All" });
TestRouteMatch("~/Customer/List/All/Delete", "Customer", "List", new { id = "All", catchall = "Delete" });
TestRouteMatch("~/Customer/List/All/Delete/Perm", "Customer", "List", new { id = "All", catchall = "Delete/Perm" });
}
}最后還是再推薦一下Adam Freeman寫的apress.pro.asp.net.mvc.4這本書。稍微熟悉MVC的從第二部分開始讀好了。前面都是入門（對我來說是扯淡）。但總比國內(nèi)某些寫書的人好吧——把個開源項(xiàng)目的源代碼下載下來帖到書上面來，然后標(biāo)題起個深入解析XXXX，然后凈瞎扯淡。最后一千多頁的巨著又誕生了。Adam Freeman的風(fēng)格我就很喜歡，都是實(shí)例寫作，然后還在那邊書里面專門寫了大量的測試。
關(guān)于“ASP.NET MVC路由配置的示例分析”這篇文章就分享到這里了，希望以上內(nèi)容可以對大家有一定的幫助，使各位可以學(xué)到更多知識，如果覺得文章不錯，請把它分享出去讓更多的人看到。
當(dāng)前標(biāo)題：ASP.NETMVC路由配置的示例分析
文章出自：http://jinyejixie.com/article16/pggsgg.html
成都網(wǎng)站建設(shè)公司_創(chuàng)新互聯(lián)，為您提供微信小程序、電子商務(wù)、云服務(wù)器、Google、網(wǎng)站建設(shè)、靜態(tài)網(wǎng)站
聲明：本網(wǎng)站發(fā)布的內(nèi)容（圖片、視頻和文字）以用戶投稿、用戶轉(zhuǎn)載內(nèi)容為主，如果涉及侵權(quán)請盡快告知，我們將會在第一時間刪除。文章觀點(diǎn)不代表本網(wǎng)站立場，如需處理請聯(lián)系客服。電話：028-86922220；郵箱：631063699@qq.com。內(nèi)容未經(jīng)允許不得轉(zhuǎn)載，或轉(zhuǎn)載時需注明來源： 創(chuàng)新互聯(lián)
- 網(wǎng)站設(shè)計公司的技術(shù)人員有哪些？ 2018-07-27
- 深圳企業(yè)網(wǎng)站設(shè)計公司9個提高用戶體驗(yàn)的方法 2014-05-13
- 北京先進(jìn)的網(wǎng)站建設(shè)公司和網(wǎng)站設(shè)計公司 2021-02-10
- 上海網(wǎng)站建設(shè)公司、上海網(wǎng)站設(shè)計公司在建設(shè)的過程中要帶給人樂趣 2020-11-04
- 請成都網(wǎng)站設(shè)計公司做專業(yè)網(wǎng)站建設(shè)有啥好處？ 2022-06-28
- 上海網(wǎng)站設(shè)計公司、上海網(wǎng)站建設(shè)公司，網(wǎng)站建設(shè)最主要的建站公司 2020-11-07
- 專業(yè)的網(wǎng)站設(shè)計公司如何設(shè)計導(dǎo)航欄才好 2021-03-31
- 威海網(wǎng)站設(shè)計公司哪幾家做得比較好 2014-01-26
- 選擇深圳網(wǎng)站設(shè)計公司有那些注意事項(xiàng)？ 2022-06-05
- 成都網(wǎng)站設(shè)計公司解析做好網(wǎng)站設(shè)計要分四步走 2016-07-05
- 上海網(wǎng)站建設(shè)公司、上海網(wǎng)站設(shè)計公司在小說網(wǎng)站中占據(jù)了多高的地位 2020-11-06
- 網(wǎng)站設(shè)計公司加大在信息安全方面的投資 2022-10-13