blocks|key|412985|text|这可能是管理所有路径或其某些变体的可行方法，例如在XML文件中定义路径|type|unstyled|depth|inlineStyleRanges|entityRanges|data|412986|http://www.iansuttle.com/blog/post/ASPNET-MVC-Store-Routes-in-the-Database.aspx|offset|length|412987|您最终仍然会有大量的路由，但是管理它们将会简单得多|412988|entityMap|0|LINK|mutability|MUTABLE|url|http://web.archive.org/web/20131113124137/http://www.iansuttle.com/blog/post/ASPNET-MVC-Store-Routes-in-the-Database.aspx^0|0|0|27|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

This might be a viable way to manage all your routes - or some variation of it such as defining the routes in an XML file

<a href="http://web.archive.org/web/20131113124137/http://www.iansuttle.com/blog/post/ASPNET-MVC-Store-Routes-in-the-Database.aspx" rel="nofollow">http://www.iansuttle.com/blog/post/ASPNET-MVC-Store-Routes-in-the-Database.aspx</a>

you'll still end up with a large number of routes but managing them would be a hell of a lot easier

blocks|key|3461582|text|我不确定这是不是正确的方法，至少不是你发布的方式。url中应该有一些定义区域性的内容，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3461583|3461584|http://example.org/en/Products/Categories|unordered-list-item|offset|length|3461585|http://example.org/de/Produkte/Kategorien|3461586|3461587|否则，您可能会得到一个在两种或更多语言/文化之间不明确的url。|3461588|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|15|0|0|0|15|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|W|8|@]|9|@$F|X|G|Y|1|Z]]|A|$]]|$1|H|3|I|5|E|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|J|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|15|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|D]]|T|$5|P|Q|R|A|$S|I]]]]

I'm not sure if it is the the right approach, at least not the way you have posted.
There should be something in the url that defines the culture, something like:

<ul>
<li><a href="http://example.org/en/Products/Categories" rel="nofollow">http://example.org/en/Products/Categories</a></li>
<li><a href="http://example.org/de/Produkte/Kategorien" rel="nofollow">http://example.org/de/Produkte/Kategorien</a></li>
</ul>

Otherwise you may end up with a url that is ambiguous between two or more languages/cultures.

blocks|key|410577|text|你可以试试我刚刚找到的一个很棒的AttributeRouting项目！你可以通过NuGet获取它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|410578|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mccalltd/AttributeRouting/wiki/Localization|1|https://nuget.org/packages/AttributeRouting^0|G|G|0|14|5|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

You can try the awesome <a href="https://github.com/mccalltd/AttributeRouting/wiki/Localization" rel="nofollow">AttributeRouting</a> project that I just found! You can get it through <a href="https://nuget.org/packages/AttributeRouting" rel="nofollow">NuGet</a>.

blocks|key|3248337|text|参见this+page，MvcCodeRouting可以选择格式化或转换路由。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3248338|entityMap|0|LINK|mutability|MUTABLE|url|http://mvccoderouting.codeplex.com/wikipage?title=Route%2BFormatting|1|http://mvccoderouting.codeplex.com/^0|2|9|0|C|E|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

<a href="http://mvccoderouting.codeplex.com/" rel="nofollow">MvcCodeRouting</a> has the option to format or translate routes, see <a href="http://mvccoderouting.codeplex.com/wikipage?title=Route+Formatting" rel="nofollow">this page</a>.

blocks|key|3248398|text|尝试使用自定义路由。这比这里提供的替代方案要灵活得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3248399|using+System;
using+System.Collections.Generic;
using+System.Linq;
using+System.Text;
using+System.Web.Routing;
using+System.Web;
using+System.Web.Mvc;

public+class+ProductRoute+:+RouteBase
{

++++public+override+RouteData+GetRouteData(HttpContextBase+httpContext)
++++{
++++++++RouteData+result+=+null;

++++++++string+virutalPath+=+httpContext.Request.Url.AbsolutePath.Substring(1).ToLowerInvariant();

++++++++//+Call+the+database+here+to+retrieve+the+productId+based+off+of+the+virtualPath
++++++++var+productId+=+Product.GetProductIdFromVirtualPath(virutalPath);
++++++++if+(productId+!=+Guid.Empty)
++++++++{
++++++++++++result+=+new+RouteData(this,+new+MvcRouteHandler());
++++++++++++result.Values["controller"]+=+"Product";
++++++++++++result.Values["action"]+=+"Details";
++++++++++++result.Values["id"]+=+productId;
++++++++}

++++++++return+result;
++++}

++++public+override+VirtualPathData+GetVirtualPath(RequestContext+requestContext,+RouteValueDictionary+values)
++++{
++++++++VirtualPathData+result+=+null;
++++++++string+controller+=+Convert.ToString(values["controller"]);
++++++++string+action+=+Convert.ToString(values["action"]);

++++++++if+(controller+==+"Product")
++++++++{
++++++++++++string+path+=+string.Empty;
++++++++++++if+(action+==+"Details")
++++++++++++{
++++++++++++++++Guid+productId+=+(Guid)values["id"];

++++++++++++++++//+Call+the+database+here+to+get+the+Virtual+Path
++++++++++++++++var+virtualPath+=+Product.GetVirtualPathFromProductId(productId);
++++++++++++}

++++++++++++if+(!String.IsNullOrEmpty(virtualPath))
++++++++++++{
++++++++++++++++result+=+new+VirtualPathData(this,+virtualPath);
++++++++++++}
++++++++}


++++++++return+result;
++++}

}|code-block|syntax|javascript|3248400|您可以通过将路由直接添加到Global.asax中的路由表来使用路由，如下所示：|3248401|++++public+static+void+RegisterRoutes(RouteCollection+routes)
++++{
++++++++routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

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


++++++++//+Add+your+custom+route+like+so
++++++++routes.Add(new+ProductRoute());


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

++++}|3248402|然后，在本地化的product表上，只需有一个包含要查找的路径的字段(没有前导斜杠)。当然，您没有提到您是如何存储数据的，所以您必须自己想出解决方案。|3248403|此外，您还需要通过在virtualPath之外解析本地化来处理本地化。根据谷歌的说法，它应该在那里。您应该根据传递的标头处理初始区域性，并将其重定向(302)到所选区域性的url。然后，用户应该能够切换语言，在这种情况下，您可以将其放入cookie中，以便记住他们的首选项。但是，搜索引擎应该能够在不传递任何标头的情况下从URL中分辨出区域性。|3248404|这将通过GetVirtualPath()方法处理@Html.RenderAction()的情况，如果需要，您可以修改逻辑。我建议您添加缓存，因为这将使每个请求按原样命中数据库。路由表是在应用程序启动时填充的，但每个路由都会在每次请求时执行。|3248405|还有一件事-要处理“路由不匹配”的情况，只需返回null，路由器就会转到下一个配置的路由。这允许您根据需要配置任意数量的自定义路由，而无需混合逻辑。|3248406|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Try using a custom route. This is much more flexible than the alternatives presented here. 

<pre><code>using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Web.Routing;
using System.Web;
using System.Web.Mvc;

public class ProductRoute : RouteBase
{

 public override RouteData GetRouteData(HttpContextBase httpContext)
 {
 RouteData result = null;

 string virutalPath = httpContext.Request.Url.AbsolutePath.Substring(1).ToLowerInvariant();

 // Call the database here to retrieve the productId based off of the virtualPath
 var productId = Product.GetProductIdFromVirtualPath(virutalPath);
 if (productId != Guid.Empty)
 {
 result = new RouteData(this, new MvcRouteHandler());
 result.Values["controller"] = "Product";
 result.Values["action"] = "Details";
 result.Values["id"] = productId;
 }

 return result;
 }

 public override VirtualPathData GetVirtualPath(RequestContext requestContext, RouteValueDictionary values)
 {
 VirtualPathData result = null;
 string controller = Convert.ToString(values["controller"]);
 string action = Convert.ToString(values["action"]);

 if (controller == "Product")
 {
 string path = string.Empty;
 if (action == "Details")
 {
 Guid productId = (Guid)values["id"];

 // Call the database here to get the Virtual Path
 var virtualPath = Product.GetVirtualPathFromProductId(productId);
 }

 if (!String.IsNullOrEmpty(virtualPath))
 {
 result = new VirtualPathData(this, virtualPath);
 }
 }


 return result;
 }

}
</code></pre>

You can use the route by adding it directly to your routes table in Global.asax, like this:

<pre><code> public static void RegisterRoutes(RouteCollection routes)
 {
 routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

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


 // Add your custom route like so
 routes.Add(new ProductRoute());


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

 }
</code></pre>

Then on your localized product table, simply have a field that contains the path to lookup (without the leading slash). Of course, you didn't mention how you are storing your data, so you will have to come up with that on your own.

Also, you will need to handle your localization by parsing it out of the virtualPath. It SHOULD be there according to Google. You should handle the initial culture based on the headers passed and redirect (302) to the url of the culture that is selected. Then the user should be able to switch the language in which case you can put it in a cookie so their preference is remembered. However, search engines should be able to tell the culture from the URL without passing any headers.

This will handle the case for @Html.RenderAction() through the GetVirtualPath() method, and you can alter the logic if needed. I recommend you add caching because this will make every request hit the database as is. The route table is populated on app startup, but each route is executed on every request.

One more thing - to handle the "route doesn't match" scenario, simply return null and the router will move on to the next configured route. This allows you to configure as many custom routes as needed without mixing logic.

blocks|key|3248430|text|有关基于属性和传统路由的的简单解决方案，请访问https://github.com/boudinov/mvc-5-routing-localization|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3248431|您可以将其与/de前缀一起使用，因为它是首选模式。您需要在资源文件中将'Products‘和'Categories’翻译成德语：|3248432|3248433|http://example.org/Products/Categories+|unordered-list-item|3248434|http://example.org/de/Produkte/Kategorien|3248435|3248436|LocalizedRoute(“~/产品/类别”，translateUrl:+true+ActionResult索引(...)|3248437|或者对原始问题的工作答案，没有语言前缀，你可以得到这样的结果：|3248438|3248439|http://example.org/Products/Categories+|3248440|http://example.org/Produkte/Kategorien|3248441|3248442|LocalizedRoute("~/Products/Categories"，translateUrl:+false，explicitCulture："en")+ActionResult索引(...)|3248443|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/boudinov/mvc-5-routing-localization|1|http://example.org/Products/Categories|2|3|4^0|N|1I|0|0|0|0|0|12|1|0|0|15|2|0|0|0|0|0|0|12|3|0|0|12|4|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@$A|1C|B|1D|1|1E]]|C|$]]|$1|D|3|E|5|6|7|1F|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|1H|8|@]|9|@$A|1I|B|1J|1|1K]]|C|$]]|$1|J|3|K|5|I|7|1L|8|@]|9|@$A|1M|B|1N|1|1O]]|C|$]]|$1|L|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1R|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1S|8|@]|9|@]|C|$]]|$1|R|3|S|5|I|7|1T|8|@]|9|@$A|1U|B|1V|1|1W]]|C|$]]|$1|T|3|U|5|I|7|1X|8|@]|9|@$A|1Y|B|1Z|1|20]]|C|$]]|$1|V|3|-4|5|6|7|21|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|22|8|@]|9|@]|C|$]]|$1|Y|3|-4|5|6|7|23|8|@]|9|@]|C|$]]]|Z|$10|$5|11|12|13|C|$14|15]]|16|$5|11|12|13|C|$14|17]]|18|$5|11|12|13|C|$14|K]]|19|$5|11|12|13|C|$14|17]]|1A|$5|11|12|13|C|$14|U]]]]

A simple solution for both attribute and conventional-based routing can be found at <a href="https://github.com/boudinov/mvc-5-routing-localization" rel="nofollow noreferrer">https://github.com/boudinov/mvc-5-routing-localization</a> 

You can get these working with /de prefix, as it is the preferred schema. You need to have 'Products' and 'Categories' translated to German in a resource file:

<ul>
<li><a href="http://example.org/Products/Categories" rel="nofollow noreferrer">http://example.org/Products/Categories</a> </li>
<li><a href="http://example.org/de/Produkte/Kategorien" rel="nofollow noreferrer">http://example.org/de/Produkte/Kategorien</a>

<pre><code>[LocalizedRoute("~/Products/Categories", translateUrl: true]
ActionResult Index(...)
</code></pre></li>
</ul>

Or working answer to the original question, without the language prefix, you can get like this: 

<ul>
<li><a href="http://example.org/Products/Categories" rel="nofollow noreferrer">http://example.org/Products/Categories</a> </li>
<li><a href="http://example.org/Produkte/Kategorien" rel="nofollow noreferrer">http://example.org/Produkte/Kategorien</a>

<pre><code>[LocalizedRoute("~/Products/Categories", translateUrl: false, explicitCulture: "en")]
[LocalizedRoute("~/Produkte/Kategorien", translateUrl: false, explicitCulture: "de")]
ActionResult Index(...)
</code></pre></li>
</ul>

Anyone knows a nice solution to localize routes in ASP.NET MVC? What I'd like to achieve is that these two urls point to the same action/resource:

<ul>
<li><a href="http://example.org/Products/Categories">http://example.org/Products/Categories</a> (en)</li>
<li><a href="http://example.org/Produkte/Kategorien">http://example.org/Produkte/Kategorien</a> (de)</li>
</ul>

Also there should be the possibility to generate the routes according to the current culture (or the default, if there are no translations available). Alternately, if I was able to specify just one culture so that only one of the two links above would work, that'd be also viable.

I tried a <a href="http://blog.maartenballiauw.be/post/2010/01/26/Translating-routes-%28ASPNET-MVC-and-Webforms%29.aspx">very nice approach by Maarten Balliauw</a>, but his solution unfortunately doesn't work with <code>Html.RenderAction(...)</code>.

Of course I could just add routes for all translations like

<pre><code>routes.MapRoute(
 "Products_Categories",
 "Produkte/Kategorien",
 new { controller = "Products", action = "Categories" }
);
</code></pre>

but that would end up in an enormous amount of routes and it'd be very unflexible. Any better solution would be appreciated :-) The more flexible the better.

Localizing/translating routes in ASP.NET MVC

数据库

路由器

路由

有谁知道在ASP.NET MVC中本地化路由的好办法吗？我想要实现的是这两个urls指向相同的操作/资源： (en) (de)此外，还应该可以根据当前文化(如果没有可用的翻译，则为默认文化)生成路由。或者，如果我能够指定一个区域性，这样上面的两个链接中只有一个可以工作，那也是可行的。我尝试了，但不幸的是，他的解决方案不...

问在ASP.NET MVC中本地化/转换路由
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ASP.NET MVC中本地化/转换路由EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ASP.NET MVC中本地化/转换路由
EN