当前位置：文江博客话题详情

如何在 ASP.NET MVC 中创建返回没有控制器引用的 URL 的路由

发布于 2024-08-20 17:03:58 字数 312 浏览 4 评论 0原文

我有一个名为 DefaultController 的控制器。在这个控制器中，我有相当于静态页面的视图。

URL 看起来像 www.site.com/Default/PageName

是否可以创建一个将这些 URL 格式化为如下形式的路由：

www.site.com/PageName

我想避免为每个都创建控制器。另一种方法是在根目录中创建 .aspx 页面，但我可以为这些页面创建路由，即：

www.site.com/PageName.aspx 变为 www.site.com/PageName 吗？

谢谢！

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

标点 2024-08-27 17:03:58

您可以为 DefaultController 上的 PageName 操作创建显式路由，如下所示：

routes.MapRoute(
    "PageName",
    "pagename",
    new { controller = "DefaultController", action = "PageName" }
);

您必须将此路由放在默认 MVC 路由之前。这种方法的最大缺点是您必须为每个静态页面创建一个路由。

另一种方法是在默认 MVC 路由之后添加一个额外的路由：

routes.MapRoute(
    "DefaultController",
    "{page}/{*path}",
    new { controller = "DefaultController", action = "{page}" }
);

这种方法的缺点是该规则将处理所有 URL，甚至是那些通常返回 404 的 URL。

You can create explicit route for the PageName action on the DefaultController like this:

routes.MapRoute(
    "PageName",
    "pagename",
    new { controller = "DefaultController", action = "PageName" }
);

You have to put this route before the default MVC route. The biggest drawback for this approach is that you have to create one route per static page.

An alternative approach would be to add an additional route after the default MVC route:

routes.MapRoute(
    "DefaultController",
    "{page}/{*path}",
    new { controller = "DefaultController", action = "{page}" }
);

The drawback for this approach is that this rule would be handling all the URLs, even those that would normally return 404.

回复收藏 0 原文

爱殇璃 2024-08-27 17:03:58

第一种方法

创建一个捕获操作的路由：

routes.MapRoute(
    "Catcher1",
    "{action}",
    new { controller = "Default", action = string.Empty });

但这意味着您必须在默认控制器上创建同样多的控制器操作。

第二种方法

如果您也想避免这种情况并且只有一个控制器+操作，请以这种方式编写路线：

routes.MapRoute(
    "Catcher2",
    "{path}",
    new { controller = "Default", action = "PageName", path = string.Emtpy },
    new { path = @"[a-zA-Z0-9]+" });

此路线还定义了路线约束，因此它只会捕获那些在第一个路线段中实际上有某些内容的路线。您可以定义此约束以仅捕获您需要的那些请求（即 path = "Result|Search|Whatever"），

然后您的 DefaultController 将具有如下内容

public ActionResult PageName(string path)
{
    // code goes here
}

：方法似乎非常可行，但我不会推荐它，因为所有逻辑都必须经过此控制器操作（对于此类请求）。最好将这些操作分成逻辑操作。那些实际上做同样事情的（这样他们就不会有一堆 switch 语句或类似的）将用单独的路由定义（如果它们不能使用单个路由来完成）。

First approach

Create a route that catches actions:

routes.MapRoute(
    "Catcher1",
    "{action}",
    new { controller = "Default", action = string.Empty });

But this means you'd have to create just as many controller actions on your default controller.

Second approach

If you'd like to avoid that as well and have just one controller+action instead, write a route this way:

routes.MapRoute(
    "Catcher2",
    "{path}",
    new { controller = "Default", action = "PageName", path = string.Emtpy },
    new { path = @"[a-zA-Z0-9]+" });

This route also defines a route constraint so it will catch only those routes, that actually have something in first route segment. You can define this constraint to only catch those requests that you need (ie. path = "Result|Search|Whatever")

then your DefaultController would have something like this:

public ActionResult PageName(string path)
{
    // code goes here
}

Second approach seems very feasible, but I wouldn't recommend it because all logic would have to go through this controller action (for these kind of requests). It would be better to separate these actions into logical ones. Those that actually do the same thing (so they wouldn't have a bunch of switch statements or similar) would be defined with separate routes (if they couldn't be done using a single one).

回复收藏 0 原文

~没有更多了~