The following is my routes definition from global.asax.cs:

以下是我在global.asax.cs中的路由定义：

routes.Add(
  new NamedTypedRoute(
    "feedback-en", RouteType.Regular, "{culture}/Feedback",
    new RouteValueDictionary(
      new
      {
        culture = "en",
        controller = "Feedback",
        action = "Index"
      }
    ),
    null,
    new MultiLingualMvcRouteHandler()
  )
);

routes.Add(
  new NamedTypedRoute(
    "feedback-sl", RouteType.Regular, "{culture}/Kontakt",
    new RouteValueDictionary(
      new
      {
        culture = "sl",
        controller = "Feedback",
        action = "Index"
      }
    ),
    null,
    new MultiLingualMvcRouteHandler()
  )
);

If I do this in the view

如果我在视图中这样做

<%: Html.ActionLink("sl", "feedback-sl")%> | <%: Html.ActionLink("en", "feedback-en")%>

the constructed URL points to the root site (no controller/action information is included in the constructed link).

构造的URL指向根站点（构造的链接中不包含控制器/操作信息）。

If I do this in the view

如果我在视图中这样做

<%: Html.RouteLink("sl", "feedback-sl")%> | <%: Html.RouteLink("en", "feedback-en")%>

an exception occurs:

发生异常：

"A route named 'feedback-sl' could not be found in the route collection.
Parameter name: name"

My two questions:

我的两个问题：

1. Why are there two very similar helpers, RouteLink and ActionLink? What's the difference between them?
2. 为什么有两个非常相似的助手，RouteLink和ActionLink？它们之间有什么区别？
3. I guess there could be something wrong with my NamedTypedRoute implementation. I need this to have named routes and typed routes - route can be admin and regular. I use this information to dynamically construct administration menu based on routes definition. For administration pages, I have names pointing to resource strings and then I use those names in administration page titles. That way I have localizable route names. Am I overcomplicating this ??
4. 我想我的NamedTypedRoute实现可能有问题。我需要这个有命名的路由和键​​入的路由 - 路由可以是管理员和常规路由。我使用此信息根据路由定义动态构建管理菜单。对于管理页面，我有指向资源字符串的名称，然后我在管理页面标题中使用这些名称。这样我就有了可本地化的路由名称。我是不是太复杂了？

1 个解决方案