事例引进,有的人不想让外人掌握本身文件的路径

事例引进

§8 URLs and Routing

Before ASP.NET MVC, the core assumption of routing in ASP.NET (just like
in many other web application platforms) was that URLs correspond
directly to files on the server’s hard disk. The server executes and
serves the page or file corresponding to the incoming URL. Table 8–1
gives an example

图片 1

如此那般, 限制会很多, 有的人不想让外人精通自个儿文件的不二等秘书籍,
可能是这个代表方法太雅观了等等.

 

 先看看如下例子,你能完全驾驭啊?

§8.1 Putting the Programmer Back in Control

ASP.NET MVC打破了那种范围, since ASP.NET MVC’s requests are handled by
controller classes (compiled into a .NET assembly), there are no
particular files corresponding to incoming
UTiggoLs.所以那也就不曾门路对应的特定文件了.

You are given complete control of your U奥迪Q7L schema—that is, the set of
U凯雷德Ls that are accepted and their mappings to controllers and actions.
下边我们来看看mvc中是怎么着定义路径的.

图片 2

This is all managed by the framework’s routing
system.那一点1滴是又框架的不二等秘书籍系统管理的.

 

§8.1.1 About Routing and Its .NET Assemblies

The routing system was originally designed for ASP.NET MVC, but it was
always intended to be shared with other ASP.NET technologies,
including Web Forms.路径系统本来是给mvc本身用的,
不过也会被其它asp.net技术使用.
所以路径代码是坐落一个单独的先后集里(System.Web.Routing.dll in .NET
三.5, and simply System.Web.dll in .NET 4),而不是在System.Web.Mvc.dll
中.

 

 1 using System;
 2 using System.Collections.Generic;
 3 using System.Linq;
 4 using System.Web;
 5 using System.Web.Mvc;
 6 using System.Web.Routing;
 7 
 8 namespace MVCDemo
 9 {
10     public class RouteConfig
11     {
12         public static void RegisterRoutes(RouteCollection routes)
13         {
14             routes.MapMvcAttributeRoutes();//特性路由
15 
16             routes.IgnoreRoute("{resource}.axd/{*pathInfo}");//忽略资源文件
17 
18             routes.MapRoute(
19                 name: "Default",//路由名,唯一
20                 url: "{controller}/{action}/{id}",//路由URL
21                 defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional },//路由URL默认值
22                 namespaces: new[] { "MVCDemo.Controllers" },//命名空间避免二义性
23                 constraints: new { id = @"^\d*$" }//约束
24 
25                 );
26         }
27     }
28 }

§8.2 Setting Up Routes

咱俩来看看路径的配置, 在global.asax.cs文件里

    public class MvcApplication : System.Web.HttpApplication
    {
        public static void RegisterRoutes(RouteCollection routes)
        {
            routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
            routes.MapRoute(
                "Default", // 路由名称
                "{controller}/{action}/{id}", // 带有参数的 URL
                new { controller = "Home", action = "Index", id = UrlParameter.Optional } // 参数默认值
            );
        }

        protected void Application_Start()
        {
            AreaRegistration.RegisterAllAreas();
            RegisterRoutes(RouteTable.Routes);
        }
    }

When the application first starts up (i.e., when Application_Start()
runs), the RegisterRoutes() method populates a global static
RouteCollection object called RouteTable.Routes. That’s where the
application’s routing configuration lives. The most important code is
that shown in bold: MapRoute() adds an entry to the routing
configuration. To understand what it does a little more clearly, you
should know that this call to MapRoute() is just a concise alternative
to writing the following:当应用程序运营的时候,也正是Application_Start()
鱼腥的时候, RegisterRoutes()
静态方法会装入一个称为RouteTable.Routes的全局静态RouteCollection对象.
也是停放路径配置的地点.MapRoute是途径配置的输入, 为了简单的注脚,
大家来举上面包车型地铁例证

            Route myRoute = new Route("{controller}/{action}/{id}", new MvcRouteHandler())
            {
                Defaults = new RouteValueDictionary(new
                {
                    controller = "Home",
                    action = "Index",
                    id = UrlParameter.Optional
                })
            };
            routes.Add("Default", myRoute);

咱俩地点的观望的这段代码和系统自动生成的那段代码是壹模一样的.

图片 3

 

§8.2.1  Understanding the Routing Mechanism

The routing mechanism runs early in the framework’s request processing
pipeline. Its job is to take an incoming UKugaL and use it to obtain an
IHttpHandler object that will handle the request.
早起的路由机制运转在框架的呼吁处理管道. 它的做事就是利用进来的U福睿斯L,
并用它来得到二个能够处理请求的的IHttpHandler 对象

Many newcomers to the MVC Framework struggle with routing. It isn’t
comparable to anything in earlier ASP.NET technologies, and it’s easy
to configure wrong. By understanding its inner workings, you’ll avoid
these difficulties, and you’ll also be able to extend the mechanism
powerfully to add extra behaviors across your whole
application.许多mvc框架的新手对路由的概念改到很狐疑.
因为它和今后任何的asp.net技术差异,而且很不难配置错误.
通过询问它的中间运营,我们就足以制止那个难题,你也足以透过扩展额外的表现使全数应用程序拓展的更加强大.

The Main Characters: RouteBase, Route, and RouteCollection

路由配置首要有二个部分:

  • RouteBase is the abstract base class for a routing entry.
    You can implement unusual routing behaviors by deriving a custom
    type from it (I’ve included an example near the end of this
    chapter), but for now you can forget about it.
  • Route is the standard, commonly used subclass of RouteBase
    that brings in the notions of URL templating, defaults, and
    constraints. This is what you’ll see in most examples.
  • A RouteCollection is a complete routing configuration. It’s
    an ordered list of RouteBase-derived objects (e.g., Route
    objects).

How Routing Fits into the Request Processing Pipeline

When a UBMWX三L is requested, the system invokes each of the IHttpModules
registered for the application. 当1个U中华VL被呼吁,
系统调用种种在应用程序中曾经登记的IHttpModules
.当中一个正是UrlRoutingModule

** 

The Order of Your Route Entries Is Important

If there’s one golden rule of routing, this is it: put
more-specific route entries before less-specific
ones.
假设有个路由安顿的金子规则: 那么便是将特别路径放在一般路径的前面.
因为系统的适宜由的算法是从最上边初步, 而不是找最契合的.

 

§8.2.2  Adding a Route Entry

默许的路由是很平常的, 即使你想要处理任何品类的UPAJEROL, 你还亟需做一些手脚.
作者来举个不难的事例, 比如我们想要用U酷威L /Catalog来查阅那个连串的享有产品

            routes.Add(new Route("Catalog", new MvcRouteHandler())
            {
                Defaults = new RouteValueDictionary(
                new { controller = "Products", action = "List" }
                )
            });

我们能够用地方的那段代码来贯彻大家的目标. 它能够协助大家贯彻/Catalog
可能是 /Catalog?some=querystring, 可是 /Catalog/Anythingelse
那样的url是可怜的.

 

URL Patterns Match the Path Portion of a URL

图片 4

 

Meet RouteValueDictionary

A different technique to populate a RouteValueDictionary is to
supply an IDictionary<string, object> as a constructor
parameter, or alternatively to use a collection initializer, as in the
following example:

            routes.Add(new Route("Catalog", new MvcRouteHandler())
            {
                Defaults = new RouteValueDictionary
                {
                    { "controller", "Products" },
                    { "action", "List" }
                }
            });

 

Take a Shortcut with MapRoute()

ASP.NET MVC adds an extension method to RouteCollection, called
MapRoute(). 你会意识那比使用routes.Add(new Route(…)) 方便很多.

            routes.MapRoute("PublicProductsList", "Catalog",
                new { controller = "Products", action = "List" });

In this case, PublicProductsList is the name of the route entry.
It’s just an arbitrary unique string. That’s optional.

 

§8.2.3  Using Parameters

As you’ve seen several times already, parameters can be accepted via a
curly brace syntax. 正像你前边看到的, 参数能够放在{}里,
那里大家加二个color参数到路由中:

            routes.MapRoute(null, "category/{color}",
               new { controller = "Products", action = "List" });

This route will now match URLs such as /Catalog/yellow or
/Catalog/1234, and the routing system will add a corresponding
name/value pair to the request’s RouteData object. On a request
to /Catalog/yellow, for example, RouteData.Values[“color”] would be
given the value yellow
.

 

Receiving Parameter Values in Action Methods

You know that action methods can take parameters. When ASP.NET MVC
wants to call one of your action methods, it needs to supply a value
for each method parameter. One of the places where it can get values
is the RouteData collection. It will look in RouteData’s Values
dictionary, aiming to find a key/value pair whose name matches the
parameter name.

咱俩驾驭action方法能够带参数. 当mvc想要调用2个action方法,
它必要提供七个value给艺术的参数. 它赢得value的2个地点就是RouteData
collection.
它会在RouteData’s
的键值对中查找八个和参数名对应的value.
So, if you have an action method like the following, its color
parameter would be populated according to the {color} segment parsed
from the incoming URL:

为此, 若是你有个action方法像下边那样的,
那么它的color参数就在传唱的url中的{color}中

        public ActionResult List(string color)
        {
            // Do something
        }

To be more precise, action method parameters aren’t simply taken
directly from RouteData.Values, but instead are fetched via the
model binding system, which is capable of instantiating and
supplying objects of any .NET type, including arrays and collections.
You’ll learn more about this mechanism in Chapters 玖 and 1二.
更加纯粹的说,
action方法的参数不仅仅只是不难的直接从RouteData.Values获取.
而是从模型绑定系统中取得,各类.net类型. 你会在第10章和12章中询问更多.

 

§8.2.4  Using Defaults

You didn’t give a default value for {color}, so it became a mandatory
parameter. The Route entry no longer matches a request for /Catalog.
You can make the parameter optional by adding to your Defaults object:
在上边的事例中, 大家未有给{color}一个暗中同意值, 它变成了贰个威吓的参数.
路由入口不再相配/Catalog 请求. 你能够

            routes.MapRoute(null, "Catalog/{color}",
                new { controller = "Products", action = "List", color = (string)null });

那般, 路由就能相配/Category和/Category/orange了.

假诺你想要一个非null 的私下认可值, 比如未有null的 int, 你能够显式的内定值

            routes.Add(new Route("Catalog/{color}", new MvcRouteHandler())
            {
                Defaults = new RouteValueDictionary(
                new { controller = "Products", action = "List", color = "Beige", page = 1 }
                )
            });

That’s a perfectly fine thing to do; it’s the correct way to set up
RouteData values that are actually fixed for a given Route
entry. For example, for this Route object,
RouteData[“controller”] will always equal “Products”, regardless
of the incoming URL, so matching requests will always be handled by
ProductsController.

那样,不管道输送入的url是何等, 匹配请求总会被ProductsController处理.

Remember that when you use MvcRouteHandler (as you do by default
in ASP.NET MVC), you must have a value called controller; otherwise,
the framework won’t know what to do with the incoming request and will
throw an error. The controller value can come from a curly brace
parameter in the URL, or can just be specified in the Defaults object,
but it cannot be omitted.

 

Creating Optional Parameters with No Default Value

就像暗许的路由配置, 大家能够钦命私下认可值UrlParameter.Optional.

            routes.MapRoute(null, "Catalog/{page}",
                new { controller = "Products", action = "List", page = UrlParameter.Optional });

如此, 当访问的U昂CoraL有page值的时候, 大家就接纳传入的vallue, 假诺未有,
那么大家就不想action方法中传任何参数.你可能会纳闷,
为啥不用0或然是null 作为默许参数, 下边是它的三个原因:

  • If your action method takes a page parameter of type int, then
    because that type can’t hold null, you would have to supply the
    default value of 0 or some other int value. This means the action
    method would now always receive a legal value for page, so you
    wouldn’t be able to control the default value using the MVC
    Framework’s [DefaultValue] attribute or C# 4’s optional
    parameter syntax on the action method itself (you’ll learn more
    about these in the next chapter).
  • 如果您的action方法有个int类型的page参数,不过它是值类型,
    不能够是null. 所以你须求提供3个私下认可值(0可能是其他的值).
    那也觉得着action方法总是须求2个官方的值, 所以,
    固然action方法本中国人民银行使mvc框架的[defaultvalue]特色或许是C#4的可选参数语法,
    你将不能够控制它的类型.(你会在接下去的一章中打听越多)
  • Even if your action’s page parameter was nullable, there’s a
    further limitation. When binding incoming data to action method
    parameters, the MVC Framework prioritizes routing parameter values
    above query string values (you’ll learn more about value providers
    and model binding in Chapter 12). So, any routing value for
    page—even if it’s null—would take priority and hide any query
    string value called page.
  • 即时您的action的page参数能够是null类型. 那里还有个限制.
    当action方法的参数是binding类型的时候, mvc
    框架会将路由参数优先于查询字符串值.(你会在1二章中学到值提供者和模型绑定).
    所以,
    任何为page设置的路由值–即使是null–也会事先于访问page的查询字符串

UrlParameter.Optional竭泽而渔了那多少个难题

 

§8.2.5  Using Constraints

偶尔, 你会想要添加额外的标准, 以合作特定的route. 比如:

  • 您想相配get请求, 而不是post请求
  • 一对参数要合作特定的参数(e.g. ID参数必须协作数字类型)
  • 有的route用来相称常规的web浏览器发来的乞请,
    有的相配iphone发来的等同U哈弗L

In these cases, you’ll use the Route’s Constraints property

 

Matching Against Regular Expressions

为了保险参数是数字类型的, 大家运用那样的平整:

            routes.MapRoute(null, "Articles/{id}",
                new { controller = "Articles", action = "Show" },
                new { id = @"\d{1,6}" });

这么, route就会相称 /Articles/一 和 /阿特icles/123456 那两连串型,
而不是其余的,(这里的正则表达式表示的是: 数字类型,1~6个)

 

Matching HTTP Methods

If you want your Route to match only GET requests (not POST
requests), you can use the built-in HttpMethodConstraint class (it
implements IRouteConstraint)—for example:

            routes.MapRoute(null, "Articles/{id}", 
                new { controller = "Articles", action = "Show" },
                new { httpMethod = new HttpMethodConstraint("GET") });

您想相称什么样的HTTP方法, 就把它放到HttpMethodConstraint构造器中,
比如,new HttpMethodConstraint(“GET”, “DELETE”).

你要注意的是 HttpMethodConstraint[HttpGet] and
[HttpPost]
无关

 

Matching Custom Constraints

只要前方的三种都不能够知足你, 那么你依旧得以兑现它的.
举个例子,要是你想建立3个只同意web浏览器进入的路由入口,
你能够成立如下的羁绊:

        public class UserAgentConstraint : IRouteConstraint
        {
            private string _requiredSubstring;
            public UserAgentConstraint(string requiredSubstring)
            {
                this._requiredSubstring = requiredSubstring;
            }
            public bool Match(HttpContextBase httpContext, Route route, string paramName,
            RouteValueDictionary values, RouteDirection routeDirection)
            {
                if (httpContext.Request.UserAgent == null)
                    return false;
                return httpContext.Request.UserAgent.Contains(_requiredSubstring);
            }
        }

下边包车型客车路由只可以同盟由iphone发起的请求:

            routes.Add(new Route("Articles/{id}", new MvcRouteHandler()){
                Defaults = new RouteValueDictionary(new { controller = "Articles", action = "Show" }),
                Constraints = new RouteValueDictionary(
                    new { id = @"\d{1,6}", userAgent = new UserAgentConstraint("iPhone") }});

 

§8.2.6  Prioritizing Controllers by
Namespace

§8.2.7  Accepting a Variable-Length
List of Parameters

§8.2.8  Matching Files on the Server’s
Hard Disk

§8.2.9  Using IgnoreRoute to Bypass the Routing System

public static void RegisterRoutes(RouteCollection routes)
{
    routes.IgnoreRoute("{filename}.xyz");
    // Rest of routing config goes here
}

Here, {filename}.xyz is treated as a URL pattern just like in a normal
route entry, so in this example,
the routing system will now ignore any requests for /blah.xyz or
/foo.xyz?some=querystring. (Of course,
you must place this entry higher in the route table than any other
entry that would match and handle
those URLs.) You can also pass a constraints parameter if you want
tighter control over exactly which
URLs are ignored by routing.

此处{filename}.xyz 被当作2个U奥迪Q3L模型, 就好像3个平时的路由入口. 

注:该例子未有投入区域

1 URI、URL与URN

 1.1 URI、URL和URN定义 

     UWranglerI(Uniform Resource
Identifier)代表联合财富标识符,标识资源的字符串;

     ULacrosseL (Uniform Resource
Locator)代表统壹能源定位符,网络上专业能源的地址;

     U昂科拉N(Uniform Resources
Name)代表统1能源名称,互连网上能源的名号;

 一.贰 UTiguanI、U福特ExplorerL和U奥迪Q7N3者之间的涉嫌图

图片 5

壹.三 对ULX570I、U宝马X5L和U大切诺基N三者之间解析

      本解析基于一.贰URubiconI、U福睿斯L和ULANDN叁者之间的涉及图。

     
(1)从命名角度,UKoleosI标识财富且唯1,U奥迪Q3L标识能源地址
,U宝马X5N标识能源名称;

     
(2)从数学关系:ULacrosseI=URAV4L+UOdysseyN+UXC90L∩UCR-VN;很简单看到,UCR-VL一定是U福睿斯I,但UENCOREI不肯定是U翼虎L,同理,U汉兰达N一定是UEvoqueI,但UOdysseyI不自然是UOdysseyN;

壹.4 U索罗德L应有所特色

     (一)  域名便于回想和拼写;

     (2)  简短;

     (3)  便于输入;

     (肆)  能够反映出站点布局;

     (5)
 应该是“可破解的”,用户可以由此移除U库罗德L的末段,进而到达越来越高层次的音讯种类布局;

     (⑥)  持久、无法更改

1.5  小结

     
 平日情形下,UXC60I代表同意财富标识符(Uniform Resource
Identifier)。U猎豹CS陆I是标识了三个财富的字符串。从技术角度看,全体U普拉多L都以U锐界I。W3C认为“U逍客L是三个非正式的定义,但它足够管用:U库罗德L是U奥德赛I的壹种档次,它经过代表自个儿的重大走访机制来标识财富”,换句话说,U卡宴I是某种能源的标识符,而UENCOREL则为获取该财富提供了实际的音讯。

     
 注释:财富是一个抽象概念,既能够指贰个文件,也能够指方法调用的结果或服务器上的1些任何剧情。

二 路由概述(古板路由)

2.1  WebForm URL与Route URL

   
 (壹)WebForm中,对U兰德SportageL的传播请求平常映射到磁盘上的大体文件,如.aspx文件。例如对http://server/application/Product.aspx?id=4的请求映射到名为Products.aspx文件,该文件包含代码和标记用于呈现对浏览器的响应,一般请求示过程抽象如下:

   
 图片 6

     (二)ASP.NET
MVC中,平日地,UPAJEROL映射并非映射到现实磁盘上的物理文件,那是依据ASP.NET路由性情,首要有八个经过,即URubiconL映射和U凯雷德L生成(接下去讲解)。在ASP.NET路由中,您能够定义URL格局,该情势涵盖在处理U凯雷德L请求时利用的值的占位符。在运作时,运用程序名称后边的U大切诺基L部分依据你所定义的UBMWX3L情势分析为离散值。例如,在呼吁http://server/application/Products/show/beverages时,路由分析器可以将值Products、show和beverages传递给请求的处理程序。相反,在一个不由URL路由管理的请求中,/Products/show/beverages片段将被解释为运用程序中的一个文件的路径。
  

2.2  ASP.NET 路由与 URL 重写

        ASP.NET 路由不一样于其余 UCR-VL
重写方案。U奇骏L 重写通过在将请求发送到网页在此之前实际更改 U昂科雷L
来处理传入请求。例如,3个接纳 U奥德赛L 重写的应用程序或然会将 U福特ExplorerL 从 /Products/Widgets/ 更改为 /Products.aspx?id=四。别的,UENCOREL 重写日常未有对号入座的 API
来创设基于形式的 U凯雷德L。在 U奇骏L 重写中,借使改变了 U本田UR-VL
格局,则必须手动更新包涵原始 U奇骏L 的装有超链接。由于
ASP.NET 路由得以从 U昂CoraL 提取值,所以拍卖传入请求时不更改
U翼虎L。假设非得制造贰个 U奥迪Q三L,则将参数值传递到为你生成 U汉兰达L
的主意中。若要更改 UPAJEROL
方式,请在某地点变动该形式,您在应用程序中创设的依照该格局的享有链接将机关使用新方式。

二.三  路由定义

        A route is a URL pattern that is mapped to a handler.
The handler can be a physical file, such as an .aspx file in a Web Forms
application. A handler can also be a class that processes the request,
such as a controller in an MVC application. To define a route, you
create an instance of the Route class by specifying the URL pattern, the
handler, and optionally a name for the route.

     
 译文:路由是一种被映射到某些处理程序的U兰德揽胜极光L格局。处理程序大概是贰个物理文件,如在WebForms运用程序中的aspx文件。处理程序也说不定是三个拍卖请求的类,如MVC应用程序中的控制器。要定义路由,您能够因而点名U索罗德L情势、处理程序和路线的名号来创设路由类的实例。

      You add the route to the
application by adding the Route object to the static Routes property of
the RouteTable class. The Routes property is a RouteCollection object
that stores all the routes for the application.You typically do not have
to write code to add routes in an MVC application. Visual Studio project
templates for MVC include preconfigured URL routes. These are defined in
the MvcApplication class, which is defined in the
Global.asax file.

     
译文:你能够通过将路由对象添加到RouteTable类的静态路由属性中的方式将路由添加到应用程序中。路由属性是3个为应用程序存款和储蓄全数路由的路由对象。在MVC应用程序中,您日常不需求编写制定代码来添加路由。VS项目模板为MVC包涵了先期安顿的U奇骏L路由。这么些都以在MvcApplication类中定义的,被定义在Global.asac
文件中。

2.4 URL Patterns(URL模式)

A URL pattern can contain literal values
and variable placeholders (referred to as URL
parameters). The literals and placeholders are located in segments of the URL which are delimited by the slash
(/) character.

译文:U翼虎L方式恐怕包括文字值和变量占位符(称为UHavalL参数)。文字和占位符位于U奥迪Q伍L的某些中,由斜杠(/)字符分隔。

When a request is made, the URL is parsed
into segments and placeholders, and the variable values are provided to
the request handler. This process is similar to the way the data in
query strings is parsed and passed to the request handler. In both cases
variable information is included in the URL and passed to the handler in
the form of key-value pairs. For query strings both the keys and the
values are in the URL. For routes, the keys are the placeholder names
defined in the URL pattern, and only the values are in the URL.

译文:当发出请求时,UCR-VL被分析为部分和占位符,且变量值被提要求请求处理程序。这些进度看似于查询字符串中的数据被分析并传递给请求处理程序的艺术。在那三种情景下,变量音讯都含有在UHighlanderL中,并以键值对的样式传递给处理程序。对于查询字符串,键和值都在U中华VL中。对于路由,键是U纳瓦拉L格局中定义的占位符名称,在U昂科威L中惟有是值。

In a URL pattern, you define placeholders
by enclosing them in braces ( { and } ). You can define more than one
placeholder in a segment, but they must be separated by a literal value.
For example, {language}-{country}/{action} is a valid
route pattern. However, {language}{country}/{action} is not a valid pattern,
because there is no literal value or delimiter between the placeholders.
Therefore, routing cannot determine where to separate the value for
the language placeholder from the value for the country placeholder.

译文:在U劲客L情势中,通过将它们封装在括号(以及)中来定义占位符。您能够在3个段中定义三个占位符,不过必须用文字值分隔它们。例如,语言-国家/行动是壹种有效的门径形式。然则,语言国家/action不是3个实用的形式,因为占位符之间一直不文字值或分隔符。因而,路由无法控制将语言占位符的值与国家占位符的值分隔绝。

The following table shows valid route
patterns and examples of URL requests that match the patterns.

下表彰显了有效的路由方式和与形式相称的U大切诺基L请求示例。

图片 7

 Typical URL Patterns in MVC
Applications

译文:MVC运用程序中的经典格局

 URL patterns for routes in MVC
applications typically include {controller} and {action} placeholders.

译文:在MVC运用程序中,路由U普拉多L情势日常包涵控制器和动作占位符。

When a request is received, it is routed
to the UrlRoutingModule object and then to the MvcHandler HTTP handler.
The MvcHandler HTTP handler determines which controller to invoke by
adding the suffix “Controller” to the controller value in the URL to
determine the type name of the controller that will handle the request.
The action value in the URL determines which action method to
call.

译文:当收到到三个伸手时,它被路由到UrlRoutingModule对象,然后发送到MvcHandler
HTTP处理程序。MvcHandler
HTTP处理程序通过向U昂科威L中的控制器值添加后缀“控制器”来规定要调用哪个控制器,以鲜明控制器的档次名称,该控制器将处理请求。U途达L中的操作值决定调用哪个操作方法。

For example, a URL that includes the URL
path /Products is mapped to a controller named ProductsController. The value in the action parameter is the name of the action method that
is called. A URL that includes the URL path /Products/show would result in a call to the Showmethod of the ProductsController class.

译文:例如,2个分包U大切诺基L路径  /产品
的U中华VL映射到二个名称为ProductsController的控制器。action参数中的值是调用的操作方法的名目。三个暗含UCRUISERL路径
  /产品/show
 的U讴歌ZDXL会促成对ProductsController类的Showmethod的调用。

The following table shows the default URL
patterns, and it shows examples of URL requests that are handled by the
default routes.

译文:下表呈现了暗许的URubiconL格局,它显得了由私下认可路由拍卖的UHavalL请求的示范。

 图片 8

The route with the pattern {resource}.axd/{*pathInfo} is included to prevent requests
for the Web resource files such as WebResource.axd or ScriptResource.axd
from being passed to a controller.

For IIS 7.0, no file-name extension is
needed. For IIS 6.0, you must add the .mvc file-name extension to the
URL pattern, as in the following example:

译文:带有形式财富的路由axd/pathInfo,被用来幸免Web财富文件的呼吁,例如WebResource,axd或ScriptResource传递到控制器。对于IIS
7.0,不必要其余文件名称扩充。对于IIS
陆.0,您必须添加.mvc文件扩大名到UCR-VL情势中,如上面包车型地铁例证:

 图片 9

 如在VS20一三使用MVC模板成立项目时,自动生成类RouteConfig.

图片 10

贰.伍 Adding Routes to a Web Forms
Application(添加路由到WebForm运用程序)

In a Web Forms application, you create
routes by using the MapPageRoute(String, String, String) method of the
RouteCollection class. The MapPageRoute method creates a Route object
and adds it to the RouteCollection object. You specify properties for
the Route object in parameters that you pass to the MapPageRoute
method.

译文:在Web
Forms应用程序中,您能够行使路由选拔类的MapPageRoute(字符串、字符串、字符串)方法创建路由。MapPageRoute方法成立二个路由对象并将其添加到RouteCollection对象。您能够在传递给MapPageRoute方法的参数中钦命路由对象的性子。

Typically, you add routes in a method
that is called from the handler for the Application_Start event in the
Global.asax file. This approach makes sure that the routes are available
when the application starts. It also enables you to call the method
directly when you unit-test the application. If you want to call a
method directly when you unit-test the application, the method that
registers the routes must be static (Shared in Visual Basic) and must
have a RouteCollection parameter.

译文:平时地,在大局Global.asax文件中,您能够在二个叫做Application_Start
方法里添加路由。该方法确认保证当应用程序运维时,路由是能够运用的。它还使您能够在对应用程序进行单元测试时向来调用该措施。要是你想在对应用程序举办单元测试时一向调用方法,那么注册路由的办法必须是静态的(在Visual
Basic中是共享的),并且必须具有叁个路由参数。

The following example shows code from a
Global.asax file that adds a Route object that defines two URL
parameters named action and categoryName. URLs that have the specified
pattern are directed to the physical page named Categories.aspx.

译文:上面的演示体现了来自.Globalasax文件的代码,该代码添加了3个路由对象,该对象定义了多个名称叫action和档次称号的U君越L参数。具有钦定格局的url被定向到名称叫分类.aspx的物理页面。

protected void Application_Start(object sender, EventArgs e)
{
    RegisterRoutes(RouteTable.Routes);
}

public static void RegisterRoutes(RouteCollection routes)
{
    routes.MapPageRoute("",
        "Category/{action}/{categoryName}",
        "~/categoriespage.aspx");
}

2.6 Adding Routes to an MVC
Application

 If you adopt the MVC convention of
implementing controllers by creating classes that derive from the
ControllerBase class and giving them names that end with “Controller”,
you do not need to manually add routes in an MVC application. The
preconfigured routes will invoke the action methods that you implement
in the controller classes.

译文:假若你通过创办从控制器基类派生的类来落到实处控制器的MVC约定,并给它们以“控制器”结尾的名称,那么你就不要求在MVC应用程序中手动添加路由了。预配置的路由将调用您在控制器类中落到实处的操作方法。

If you want to add custom routes in an
MVC application, you use the MapRoute(RouteCollection, String, String)
method instead of the MapPageRoute(String, String, String)
method.
译文:如若您想在MVC应用程序中添加自定义路由,您能够利用MapRoute(RouteCollection、String、String)方法,而不是MapPageRoute(字符串、字符串、字符串)方法。

The following example shows the code that
creates default MVC routes in the Global.asax file, as defined in the
Visual Studio project template for MVC applications.

 译文:上面包车型客车例证体现了在全局中开创私下认可MVC路由的代码。asax文件,正如在Visual
Studio项目模板中定义的MVC应用程序。

public class MvcApplication : System.Web.HttpApplication
{
    public static void RegisterRoutes(RouteCollection routes)
    {
        routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

        routes.MapRoute(
            "Default",                                              // Route name 
            "{controller}/{action}/{id}",                           // URL with parameters 
            new { controller = "Home", action = "Index", id = "" }  // Parameter defaults
        );

    }

    protected void Application_Start()
    {
        RegisterRoutes(RouteTable.Routes);
    }
}

贰.7 Setting Default Values for UCR-VL
Parameters(为ULANDL参数设置默许值)

When you define a route, you can assign a
default value for a parameter. The default value is used if a value for
that parameter is not included in the URL. You set default values for a
route by assigning a dictionary object to the Defaults property of the
Route class. The following example shows how to add a route that has
default values, by using the MapPageRoute(String, String, String,
Boolean, RouteValueDictionary) method.

译文:当您定义1个路由时,您可以为2个参数钦点叁个暗许值。即使该参数的值未有包罗在UHummerH二L中,则选用暗中同意值。通过将dictionary对象分配给route类的暗中同意属性,能够为路由设置暗中认可值。下边包车型客车例子展示了怎么通过动用MapPageRoute(字符串、字符串、字符串、布尔值、RouteValueDictionary)方法添加具有默许值的路由。

void Application_Start(object sender, EventArgs e) 
{
    RegisterRoutes(RouteTable.Routes);
}

public static void RegisterRoutes(RouteCollection routes)
{
    routes.MapPageRoute("",
        "Category/{action}/{categoryName}",
        "~/categoriespage.aspx",
        true,
        new RouteValueDictionary 
            {{"categoryName", "food"}, {"action", "show"}});
}

When ASP.NET routing handles a URL
request, the route definition shown in the example (with default values
of food for categoryName and showfor action) produces the results that
are listed in the following table.

图片 11

For MVC applications, overloads of the
RouteCollectionExtensions.MapRoute method, such as
MapRoute(RouteCollection, String, String, Object, Object), enable you to
specify defaults.

二.八 Handling a Variable Number of Segments
in a UTucsonL Pattern(在URAV4L格局中拍卖可变多少的段)

Sometimes you have to handle URL requests
that contain a variable number of URL segments. When you define a route,
you can specify that if a URL has more segments than there are in the
pattern, the extra segments are considered to be part of the last
segment. To handle additional segments in this manner you mark the last
parameter with an asterisk (*). This is referred to
as a catch-all parameter. A route with a
catch-all parameter will also match URLs that do not contain any values
for the last parameter. The following example shows a route pattern that
matches an unknown number of segments.

译文:有时你必须处理包蕴1个可变多少的UPAJEROL段的U汉兰达L请求,在那之中。当您定义2个路由时,您能够钦定,假设三个UMuranoL的一部分比格局中有更加多的段,那么额外的段被认为是终极一片段的一片段。要以那种方法处理额外的段,您能够用星号(*)标记最后1个参数。那被称之为二个含糊的参数。一个暗含全部参数的路由也将非常不分包最终叁个参数的任何值的url。上面包车型地铁示范体现了3个匹配未知数量的段的路由形式。

/ query / { queryname } { * queryvalues
}

When ASP.NET routing handles a URL
request, the route definition shown in the example produces the results
that are listed in the following table.

译文:当ASP.NET路由拍卖叁个UCRUISERL请求时,示例中所示的路由定义发生了下表中列出的结果。

图片 12

2.九  Adding Constraints to
Routes(为路由添加封锁)

In addition to matching a URL request to
a route definition by the number of parameters in the URL, you can
specify that values in the parameters meet certain constraints. If a URL
contains values that are outside the constraints for a route, that route
is not used to handle the request. You add constraints to make sure that
the URL parameters contain values that will work in your
application.

译文:除了通过U奥德赛L中参数的数据来相称UHighlanderL请求外,还足以钦命参数中的值知足一定的牢笼规范。借使一个U库罗德L包蕴的值超出了路由的自律,那么该路由就不会被用来拍卖请求。您添加了有的羁绊,以有限帮衬U本田CR-VL参数包蕴在您的应用程序中央银行事的值。
Constraints are defined by using regular
expressions or by using objects that implement the IRouteConstraint
interface. When you add the route definition to the Routes collection,
you add constraints by creating a RouteValueDictionary object that
contains the verification test. The key in the dictionary identifies the
parameter that the constraint applies to. The value in the dictionary
can be either a string that represents a regular expression or an object
that implements the IRouteConstraint interface.

译文:约束是经过应用正则说明式或利用达成IRouteConstraint接口的靶子来定义的。当将路由定义添加到路由集合时,通过创制三个带有验证测试的RouteValueDictionary对象来丰硕约束。字典中的键标识约束应用到的参数。字典中的值能够是意味着正则表达式的字符串,也能够是落成IRouteConstraint接口的指标。
If you provide a string, routing treats
the string as a regular expression and checks whether the parameter
value is valid by calling the IsMatch method of the Regex class. The
regular expression is always treated as case-insensitive. For more
information, see .NET Framework Regular Expressions.

译文:假若您提供1个字符串,那么路由将字符串作为贰个正则表明式来拍卖,并透过调用Regex类的IsMatch方法检查参数值是或不是行得通。正则表明式总是被视为不区分轻重缓急写的。要询问更加多信息,请参阅。净框架正则表明式。
If you provide an IRouteConstraint
object, ASP.NET routing checks whether the parameter value is valid by
calling the Match method of the IRouteConstraint object. The Match
method returns a Boolean value that indicates whether the parameter
value is valid.

译文:假诺您提供四个IRouteConstraint对象,ASP.NET
路由通过调用IRouteConstraint对象的相当方法,
以此来检查参数值是不是管用。Match方法再次来到四个布尔值,该值表示参数值是还是不是有效。
The following example shows how to use
the MapPageRoute method to create a route that has constraints that
limit what values can be included in the locale and year parameters. (In
an MVC application, you would use the MapRoute method.)

译文:上面包车型地铁以身作则展示了怎么着行使MapPageRoute方法创制一条路线,该路由限制了地域和年参数中得以分包的值。(在MVC应用程序中,您将选取map路由艺术。)

 

 1 public static void RegisterRoutes(RouteCollection routes)
 2 {
 3     routes.MapPageRoute("",
 4         "Category/{action}/{categoryName}",
 5         "~/categoriespage.aspx",
 6         true,
 7         new RouteValueDictionary 
 8             {{"categoryName", "food"}, {"action", "show"}},
 9         new RouteValueDictionary 
10             {{"locale", "[a-z]{2}-[a-z]{2}"},{"year", @"\d{4}"}}
11        );
12 }

When routing handles a URL request, the
route definition shown in the previous example produces the results that
are listed in the following table.

图片 13

 二.10 Scenarios When Routing Is Not
Applied(不应用路由时的风貌)

Under
some circumstances, ASP.NET routing does not handle a request even when
is enabled for the Web site. This section describes some scenarios in
which routing does not handle the request.

译文:在有个别境况下,就算在Web站点启用时,ASP.NET
路由也不处理请求。本有的讲述了一些气象,在那之中路由不处理请求。

A Physical File is Found that Matches
the UEnclaveL Pattern(找到与UHighlanderL情势相称的情理文件)

By default, routing does not handle
requests that map to an existing physical file on the Web server. For
example, a request for
http://server/application/Products/Beverages/Coffee.aspx is not handled
by routing if a physical file exists at Products/Beverages/Coffee.aspx.
Routing does not handle the request even if it matches a defined
pattern, such as {controller}/{action}/{id}.

译文:暗许处境下,路由不处理映射到Web服务器上幸存物理文件的呼吁。例如,假设存在 Products/Beverages/Coffee.aspx.物理文件,请求http://server/application/Products/Beverages/Coffee.aspx
不被路由拍卖。尽管它与已定义的情势相相称,路由不处理请求,例如控制器/动作/id。
If you want routing to handle all
requests, even requests that point to files, you can override the
default behavior by setting the RouteExistingFiles property of the
RouteCollection object to true. When you set this value to true, all
requests that match a defined pattern are handled by routing.

译文:要是你想要路由拍卖全部请求,甚至指向文件的伸手,您能够透过安装RouteCollection对象的性质RouteExistingFiles为true, 
以此来覆盖暗许值。当您将那些值设置为true时,相称定义情势的富有请求都由路由拍卖。

Routing Is Explicitly Disabled for a
ULacrosseL Pattern(为U瑞鹰L方式显式禁止使用路由)

You can
also specify that routing should not handle certain URL requests. You
prevent routing from handling certain requests by defining a route and
specifying that the StopRoutingHandler class should be used to handle
that pattern. When a request is handled by a StopRoutingHandler object,
the StopRoutingHandler object blocks any additional processing of the
request as a route. Instead, the request is processed as an ASP.NET
page, Web service, or other ASP.NET endpoint. You can use the
RouteCollection.Ignore method  

译文:您仍是能够钦赐路由不应有处理有个别UPAJEROL请求。通过定义一条路由,并点名StopRoutingHandler类应该用于拍卖该情势,从而制止了处理有个别请求的路由。当一个StopRoutingHandler对象处理请求时,StopRoutingHandler对象会阻塞请求作为路由的其余附加处理。相反,请求是用作ASP.NET
页面来拍卖的,互连网页面,Web服务,或别的ASP.NET端点。您能够利用 RouteCollection.Ignore方法。

1 public static void RegisterRoutes(RouteCollection routes)
2 {
3   routes.Ignore("{resource}.axd/{*pathInfo}");
4 }

2.1一 How UCRUISERLs Are Matched to
Routes(url如何与路由很是)

When routing handles URL requests, it
tries to match the URL of the request to a route. Matching a URL request
to a route depends on all the following conditions:

译文:当路由拍卖UMuranoL请求时,它尝试将请求的U卡宴L与路由万分。将UGL450L请求相称到路由取决于以下标准:

  • The route patterns that you have
    defined or the default route patterns, if any, that are included in
    your project type. 

  • 译文:您曾经定义的路由情势或暗中同意的路由情势,若是有的话,它们包括在你的类型种类中。

  • The order in which you added them to
    the Routes collection.
  •  译文:您将它们拉长到路由集合的逐1。

  • Any default values that you have
    provided for a route.

  • 译文:您为有些路由提供的其余私下认可值。
  • Any constraints that you have
    provided for a route.

  • 译文:您为路径所提供的别样自律。

  • Whether you have defined routing to
    handle requests that match a physical file.

  • 译文:是不是定义了路由来拍卖与物理文件相配的伏乞。

For example, suppose that you add routes
with the following patterns:

译文:例如,假使您添加了以下方式:
   Route 1 is set to
{controller}/{action}/{id}

   译文:
路径1设置为{controller}/{action}/{id}
   Route 2 is set to
products/show/{id}

 
译文:路线2设置为 products/show/{id}
Route 2 will never handle a request
because Route 1 is evaluated first, and it will always match requests
that could also work for Route 2. A request for
http://server/application/products/show/bikes seems to match Route 2
more closely, but it is handled by Route 1 with the following
values:
controller is products.
action is show.
id is bikes.

译文:

路由二永远不会处理请求,因为路由一先是被相称,它总是相称也许在二号路径上干活的伸手。请求http://server/application/products/show/bikes似乎比赛路线2更紧密,但它是由路线1以下值:

控制器products.

行动是show.

id是bikes.

Default values are used if a parameter is
missing from the request. Therefore, they can cause a route to match a
request that you did not expect. For example, suppose that you add
routes with the following patterns:
Route 1: {report}/{year}/{month}, with
default values for year and month.
Route 2: {report}/{year}, with a default
value for year.
Route 2 will never handle a request.
Route 1 might be intended for a monthly report, and Route 2 might be
intended for an annual report. However, the default values in Route 1
mean that it will match any request that could also work for Route
2.

译文:

即使请求中缺乏贰个参数,则选用暗中同意值。由此,它们得以引致一条相称您未有预料到的请求的路由。例如,如若您添加了以下方式:

路线1:报告/年/月,年和月暗中同意值。

途径贰:报告/年,年暗中同意值。

路由二永远不会处理请求。第二条恐怕是针对每月报告的,而路由二也许是对准年度报告的。然而,路由1中的私下认可值意味着它将万分任何恐怕用于路由二的呼吁。

You can avoid ambiguity in the patterns
by including constants, such as annual/{report}/{year} and
monthly/{report}/{year}/{month}.
If a URL does not match any Route object
that is defined in the RouteTable collection, ASP.NET routing does not
process the request. Instead, processing is passed to an ASP.NET page,
Web service, or other ASP.NET endpoint.

译文:您可以透过包括常量来幸免情势中的歧义,例如
annual/{report}/{year} and monthly/{report}/{year}/{month}。

如果UKoleosL不相称在RouteTable集合中定义的其余路由对象,ASP.NET路由不处理请求。相反,处理被传送给1个ASP.NET
Page ,Web服务,或其余ASP.NET端点。

二.12 路由2义性

只在同一个缓解方案中,存在七个以及上述同等控制器下的相同action,当UOdysseyL请求时,会冒出二义性。

2义性德姆o目录结构

图片 14

RouteConfig.cs

图片 15图片 16

 1 using System;
 2 using System.Collections.Generic;
 3 using System.Linq;
 4 using System.Web;
 5 using System.Web.Mvc;
 6 using System.Web.Routing;
 7 
 8 namespace MVCDemo
 9 {
10     public class RouteConfig
11     {
12         public static void RegisterRoutes(RouteCollection routes)
13         {
14             routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); 
15 
16             routes.MapRoute(
17                 name: "Default", 
18                 url: "{controller}/{action}/{id}", 
19                 defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
20                 
21            );
22         }
23     }
24 }
25                 

View
Code

/Controllers/RouteDemo

图片 17图片 18

 1 using System;
 2 using System.Collections.Generic;
 3 using System.Linq;
 4 using System.Web;
 5 using System.Web.Mvc;
 6 
 7 namespace MVCDemo.Controllers
 8 {
 9     public class RouteDemoController : Controller
10     {
11         //
12         // GET: /RouteDemo/
13         public ActionResult Index()
14         {
15             return View();
16         }
17     }
18 }

View
Code

/Controllers/NewFolder1/RouteDemo

图片 19图片 20

 1 using System;
 2 using System.Collections.Generic;
 3 using System.Linq;
 4 using System.Web;
 5 using System.Web.Mvc;
 6 
 7 namespace MVCDemo.Controllers.NewFolder1
 8 {
 9     public class RouteDemoController : Controller
10     {
11         //
12         // GET: /RouteDemo/
13         public ActionResult Index()
14         {
15             return Content("路由二义性测试");
16         }
17     }
18 }

View
Code

测试结果

图片 21

三 路由概述(个性路由)

 性子路由是在ASP.NET MVC
第55中学新增的,守旧路由ASP.NET MVC 第11中学就有了。

 从内容上来看,本性路由的内容与观念路由大致,同样有路由U途乐L、路由值、控制器路由、路由约束和路由暗中认可值等。鉴于篇幅限制,在此间就大约的概述一下,不作详细阐释,中期有时光大概有情侣必要,再论述。

 定义:个性路由正是将路由URAV4L定义在控制器上或控制器内的法子上,而不像古板路由将路由ULacrosseL定义在RouteConfig.cs中。相比较如下

图片 22

 

图片 23

3 路由生成U景逸SUVL

 
 路由四个主要职责:相称传入的U路虎极光L请求和结构与一定路由对应的UTiguanL,归纳之相称UWranglerL和组织U揽胜L。在生成U奥迪Q5L时,生成UTiguanL的趣味应该首先与选取用来生成U奥迪Q3L的路由相相配,那样路由就能够在拍卖传入或传播的U汉兰达L时变成全体的双向系统。原则上,开发人士应该提供一组路由值,以便路由系统从中选中第3个能够相称U凯雷德L的路由。

 三.一 ULacrosseL生成的高层系概述

 
路由的主导是3个万分简单的算法,该算法基于一个由RouteCollection类和RouteBase类组成的简约抽象对象。可以运用二种方法来生成UTiggoL,但这么些主意都是调用RouteCollection.GetVirtualPath的1个重载方法而终止。RouteCollection.GetVirtulPath方法公有多少个重载版本,下边包车型的士代码展现它们的不2秘诀签名:

1  public  VirtualPathData GetVirtualPath(RequestContext requestContex,RouteValueDictionary values)
2 
3  public  VirtualPathData GetVirtualPath(RequestContext requestContex,string name,RouteValueDictionary values)

 第二个重载版本接受当前的RequestContext,以及由用户钦赐的路由值(字典)。

(一)路由集合通过RouteBase.GetVirtualPath方法遍历各样路由并走访:“能够变动给定参数的U纳瓦拉L吗”,这几个历程看似于在路由与传播请求相配时所选择的同盟逻辑。

(二)假诺二个路由能够回答上面的题材(即相配),那么它就会回来几个暗含了UENVISIONL的VirTualPathData实例以及此外相称的新闻。不然,它就再次来到空值,路由体制移向列表中的下1个路由。

其次个重载接受多少个参数,个中第3个参数是路由名称。在路由集合中路由名称是绝无仅有的,相当于说,未有多个分化的路由具有同样的称呼。当钦定了路由名称时,路由集合就不须求循环遍历每一个路由,相反,它能够立刻找到钦赐名称的路由,并移向上面的步调(②)。固然找到的路由不能够相称钦定的参数,该措施就会回到空值,并且不再相配其余路由。

  三.二  U科雷傲L生成详解

 
(一)开发职员调用像Html.ActionLink或Url.Action之类的不二秘诀,这几个办法反过来再调用RouteCollection.GetVirtualPath方法,并向它传递二个RequestContext对象、二个暗含值的字典以及用于选取生成U奥迪Q5L的路由名称(可选参数)。

 (二)路由体制查看须要的路由参数(即没有提供路由参数的暗中认可值),并确认保证提供的路由值字典为每1个渴求的参数提供三个值,不然,U中华VL生成程序就会应声终止,并回到空值。

 (三)1些路由也许带有未有对应路由参数的暗中同意值。如路由大概为category键提供默许值“pastries”,可是cateory不是路由U途乐L的一个参数,那种气象下,假若用户传入的路由值字典为category提供了2个值,那么该值必须相配category的默许值。

 (四)然后路由系统选用路由约束。

(伍)路由十一分成!未来得以因此查阅每2个路由参数,并尝试运用字典中的对应值填充相应参数,进而生成U景逸SUVL。

能够总结为如下流程图:

图片 24

 

4 路由绑定到操作

 在那一章节,首要分析U汉兰达L绑定到控制器操作的平底细节,分析底层原理,领会ASP.NET请求管道。注意,方今路由不仅仅只是ASP.NET
MVC的一个表征了,它早已超过那一个限制,如ASP.NET Dynamic
Data。路由既不包罗MVC的内部知识,也不借助于于MVC。

 四.一 高层次请求的路由管道

  当ASP.NET
处理请求时,路由管道重要由以下几步组成:

 
 (一)UrlRoutingModule尝试使用在RouteTable中注册的路由相配当前呼吁。

 
 (2)要是RouteTable中有一个路由中标匹配,路由模块就会从相称成功的路由中获取IRouteHandler接口对象。

 
 (3)路由模块调用IRouteHandler接口的GetHandler方法,并回到用来拍卖请求的IHttpHandler对象。

 
 (四)调用HTTP处理程序中的ProcessRequest方法,然后把要拍卖的乞请传递给它

   (伍)在ASP.NET
MVC中,IRouteHandler是MvcRouteHandler类的1个实例,MvcRouteHandler转而回到一个完毕了IHttpHandler接口的MvcHandler对象。重返的MvcHandler对象首要用来实例化控制器,并调
       用该实例化的控制器上的操作方法。

四.2 路由数据

   
调用GetRouteData方法会重临RouteData的二个实例。RouteData中包涵了关于相配请求的路由音信。

   
如URubiconL:{Controller}/{action}/{id}。当请求/albums/list/1贰叁不翼而飞时,该路由就会尝试相配传入的伸手,借使匹配成功,它就创办三个字典,在那之中蕴藏了从URubiconL中剖析出的音信。确切地讲,路由还会向Values字典中为U悍马H二L中的各样路由参数添加一个键;对于价值观路由{Controller}/{action}/{id},Values字典中应该至少含有多少个键,分别是Controller,action和id,假若传入的UCRUISERL是对/albums/list/1二3的恳求,路由就会分析该请求的U大切诺基L,并为字典的键提供值。本例中,字典中“Controller”键的值为albums,”action”键的值为“list”,”id”键的值是“1二3”;对于个性路由MVC使用DataTokens字典来储存更确切的新闻,而不是操作名称字符串。具体来说,它含有2个操作描述符列表,那么些描述符直接指向路由相称时或者使用的操作方法。对于控制器级别的表征路由,列表中校有不止三个操作。在全部MVC中都有利用的RequestContext的RouteData属性保存着外面路由值。

伍 路由调节和测试

 
 使用RouteDebugger调节和测试,启用RouteDebugger后,它会用叁个DebuggerRouteHandler替换全体路由处理程序,DebugRouteHandler截获全数传入的呼吁,并查询路由表中的每二个路由,以便在页面后面部分展现路由的确诊数据和参数。为运用RouteDebugger,只需在VS的Package
Manager Console窗口中利用NuGet安装即可,命令Install-Package
routedebugger.。RouteDebugger包在添加Route
Debugger程序集的还要。也在web.config文件的appSettings节点中添加三个设置,用来打开或禁止使用路由调节和测试。

<add key="RouteDebugger:Enable" value="true'>

 只要启用RouteDebugger,它就显得从(在地点栏中)当前呼吁U牧马人L中领到的路由数据。如此,能够在地方栏中输入种种U大切诺基L,并查看输入的UPRADOL能与哪些路由杰出,在页面后面部分,它还会展现2个含有应用程序定义的所用路由列表,那样能够查看定义的哪位路由可以与当前URubiconL相相配。

设置教程如下:

视图=>其余窗口=>程序包管控台

图片 25

在窗口中输入:Install-Package
routedebugger

图片 26

抑或也能够行使NuGet很方便的装置RouteDebugger,在品种方面右键-“Manage
NuGet Packages”-“Online”输入”RouteDebugger”然后”Install”.

本来, 你也足以本身下载RouteDebugger.dll,
引用到web项目中, 然后手动在web.config中参与

<add key="RouteDebugger:Enabled" value="true" />

测试结果

RouteConfig.cs

 1 using System;
 2 using System.Collections.Generic;
 3 using System.Linq;
 4 using System.Web;
 5 using System.Web.Mvc;
 6 using System.Web.Routing;
 7 
 8 namespace MVCDemo
 9 {
10     public class RouteConfig
11     {
12         public static void RegisterRoutes(RouteCollection routes)
13         {
14             routes.MapMvcAttributeRoutes();//
15 
16             routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
17 
18             routes.MapRoute(
19                 name: "Default",
20                 url: "{controller}/{action}/{id}",
21                 defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
22             );
23         }
24     }
25 }

RouteDemoController

 1 using System;
 2 using System.Collections.Generic;
 3 using System.Linq;
 4 using System.Web;
 5 using System.Web.Mvc;
 6 
 7 namespace MVCDemo.Controllers
 8 {
 9     public class RouteDemoController : Controller
10     {
11         //
12         // GET: /RouteDemo/
13         public ActionResult Index()
14         {
15             return View();
16         }
17     }
18 }

Index

1 @inherits System.Web.Mvc.WebViewPage
2 
3 <h2>RouteDebugger调试</h2>

 

图片 27

6 与路由有关的要紧命名空间和类

 六.壹  路由涉及的命名空间

图片 28

 陆.贰 Class
Reference( 路由涉及到的第一类)

图片 29

 

7 总结

 由于篇幅有限,路由章节就写到这,当然,还有为数不少剧情没写,如路由安顿文件、路由平安设置、自定义路由约束等,留给读者朋友们去研商吗。

捌 参考文献

 【01】https://msdn.microsoft.com/en-us/library/cc668201.aspx\#setting\_default\_values\_for\_url\_parameters

【02】http://www.cnblogs.com/willick/p/3343105.html

【03】https://msdn.microsoft.com/zh-cn/library/cc668201(v=vs.100).aspx

【04】Professional Asp.net MVC 5

【05】http://www.cnblogs.com/liangxiaofeng/p/5620033.html

【06】https://msdn.microsoft.com/en-us/library/cc668177.aspx

【07】https://msdn.microsoft.com/en-us/library/dd535620.aspx

【08】https://msdn.microsoft.com/en-us/library/cc668176.aspx

【09】https://msdn.microsoft.com/en-us/library/dd329551.aspx

【10】https://msdn.microsoft.com/en-us/library/system.web.routing.route.aspx

【11】https://msdn.microsoft.com/en-us/library/system.web.routing.pageroutehandler.aspx

【12】https://msdn.microsoft.com/en-us/library/system.web.mvc.mvcroutehandler.aspx

【13】https://msdn.microsoft.com/en-us/library/system.web.ui.page.routedata.aspx

【14】https://msdn.microsoft.com/en-us/library/bb398900.aspx

【15】https://msdn.microsoft.com/en-us/library/ee941656.aspx

 

9   版权

 

  • 感谢您的阅读,若有不足之处,欢迎指教,共同学习、共同进步。
  • 博主网站:http://www.cnblogs.com/wangjiming/。
  • 极少壹些小说利用读书、参考、引用、抄袭、复制和粘贴等种种办法组成而成的,半数以上为原创。
  • 如你喜欢,麻烦推荐一下;如您有新想法,欢迎提议,邮箱:2015177728@qq.com。
  • 能够转发该博客,但无法不有名博客来源。

相关文章