blocks|key|363769|text|你也可以看看这里，如果你使用ASP.NET+MVC2，ASP.NET+MVC+2+Localization+complete+guide和ASP.NET+MVC+2+Model+Validation+With+Localization将会对你有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|363770|entityMap|0|LINK|mutability|MUTABLE|url|http://adamyan.blogspot.com/2010/02/aspnet-mvc-2-localization-complete.html|1|http://helios.ca/2010/02/17/asp-net-mvc-2-model-validation-with-localization/^0|R|15|0|1X|1C|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 also take a look here <a href="http://adamyan.blogspot.com/2010/02/aspnet-mvc-2-localization-complete.html" rel="noreferrer">ASP.NET MVC 2 Localization complete guide</a> and <a href="http://helios.ca/2010/02/17/asp-net-mvc-2-model-validation-with-localization/" rel="noreferrer">ASP.NET MVC 2 Model Validation With Localization</a> these entires will help you if you working with ASP.NET MVC 2.

blocks|key|3149847|text|本地化Web应用程序的方式与本地化典型的ASP.NET+ASP.NET表单应用程序的方式非常相似。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3149848|您不会为每种语言使用不同的页面/视图，但每个页面将支持使用附属程序集的多种语言。|3149849|您可以查看Matt+Hawley's+blog+entry以获得更多解释和示例。|offset|length|3149850|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.eworldui.net/post/2008/05/ASPNET-MVC---Localization.aspx^0|0|0|5|O|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

You would localize your ASP.NET MVC application very much in the same way you would a classic ASP.NET Web Form application.

You wouldn't use different pages/views for each language, but each page would support multiple languages using satellite assemblies.

You can look at <a href="http://blog.eworldui.net/post/2008/05/ASPNET-MVC---Localization.aspx" rel="noreferrer">Matt Hawley's blog entry</a> for more explanation and examples.

blocks|key|3362753|text|不幸的是，Matt+Hawley的原始代码在ASP.NET+MVC的发布版本中不起作用。查看更新后的帖子：http://blog.eworldui.net/post/2008/10/ASPNET-MVC-Localization-via-View-Engines.aspx|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3362754|一般来说，在VS2008/+ASP.NET的MVC世界中，本地化过程并不像传统的web表单那样顺畅。http://www.guysmithferrier.com/post/2009/05/Localizing-ASPNET-MVC.aspx|3362755|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.eworldui.net/post/2008/10/ASPNET-MVC-Localization-via-View-Engines.aspx|1|http://www.guysmithferrier.com/post/2009/05/Localizing-ASPNET-MVC.aspx^0|1H|2B|0|0|1E|1Y|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Unfortunately, Matt Hawley's original code doesn't work in the release version of ASP.NET MVC. Check out an updated post: <a href="http://blog.eworldui.net/post/2008/10/ASPNET-MVC-Localization-via-View-Engines.aspx" rel="noreferrer">http://blog.eworldui.net/post/2008/10/ASPNET-MVC-Localization-via-View-Engines.aspx</a>

In general, the localization process isn't as smooth in the VS 2008 / ASP.NET MVC world as it is with traditional web forms. <a href="http://www.guysmithferrier.com/post/2009/05/Localizing-ASPNET-MVC.aspx" rel="noreferrer">http://www.guysmithferrier.com/post/2009/05/Localizing-ASPNET-MVC.aspx</a>

blocks|key|3149857|text|看看Rob+Connery的MvcStore项目。他做了一个截屏视频，展示了解决全球化问题的一种方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3149858|http://wekeroad.com/2008/04/24/mvcstore-part-5|offset|length|3149859|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1A|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Have a look at Rob Connery's MvcStore project. He does a screencast showing one way to solve the globalization problem.

<a href="http://wekeroad.com/2008/04/24/mvcstore-part-5" rel="nofollow noreferrer">http://wekeroad.com/2008/04/24/mvcstore-part-5</a>

blocks|key|363765|text|我从来没有像Elijah建议的那样在表单中处理本地化-不同的长度和方向可能会导致非常复杂或看起来不同的表单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|363766|我刚刚开始使用MVC，但是采用解耦方法，您希望使用相同的控制器，而不考虑语言(将语言视为视图)-这将得到/+controller+/Action/+language+/form|363767|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I've never been convinced of handling localization within a form as Elijah suggests - the different lengths and directions can lead to very complex or vary naff looking forms.

I'm only just starting with MVC but taking the decoupling method you would wan to use the same controller regardless of the language (treating language just as a view) - this would then give you /Controller/Action/language/form

blocks|key|3362797|text|有关于如何本地化asp.net+mvc应用程序的最新更新的很好的教程，涵盖了所有方面，包括DisplayName本地化，验证，使用路由(将文化名称存储在URL中)，输出缓存问题等等……Alex+Adamyan+Blog+-+While+my+keyboard+gently+weeps|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3362798|entityMap|0|LINK|mutability|MUTABLE|url|http://adamyan.blogspot.com/^0|2K|1E|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There is good tutorial with recent update on How to localize asp.net mvc application covering all aspects including DisplayName localization, Validation, using Routing (storing culture name in URL), issues with output cache and so on... <a href="http://adamyan.blogspot.com" rel="nofollow noreferrer">Alex Adamyan Blog - While my keyboard gently weeps</a>

blocks|key|361188|text|我们实际上用完全不同的方式覆盖了DataAnnotationsMetadaDataProvider。在这里，您可以确保将DisplayNameAttribute值解析为正确的语言。实际上，您甚至可以去掉该属性，只在有帮助的情况下才使用字段名进行解析。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|361189|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.mvc.dataannotationsmodelmetadataprovider%2528v=vs.108%2529.aspx^0|G|X|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

We actually went a complete different with overriding the 
<a href="http://msdn.microsoft.com/en-us/library/system.web.mvc.dataannotationsmodelmetadataprovider%28v=vs.108%29.aspx" rel="nofollow">DataAnnotationsMetadaDataProvider</a>.
In there you can make sure that the DisplayNameAttribute values are resolved into the correct language.
Actually you could even get rid of that attribute and resolve by field names only if that would be any help.

blocks|key|3362800|text|我前段时间写了这篇文章。它使用一个自定义的视图引擎。http://blog.oimae.com/2011/02/20/cultured-view-engine-for-mvc/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3362801|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.oimae.com/2011/02/20/cultured-view-engine-for-mvc/^0|Q|1Q|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I wrote this article a while ago. It uses a custom view engine.
<a href="http://blog.oimae.com/2011/02/20/cultured-view-engine-for-mvc/" rel="nofollow">http://blog.oimae.com/2011/02/20/cultured-view-engine-for-mvc/</a>

blocks|key|359116|text|和另一个针对不同解决方案的教程|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359117|Tutorial:+Create+ASP.NET+MVC+localization+with+language+detection|offset|length|359118|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.kosev.net/2010/06/tutorial-create-aspnet-mvc-localization.html^0|0|0|1T|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

And another tutorial for different solution

<a href="http://blog.kosev.net/2010/06/tutorial-create-aspnet-mvc-localization.html" rel="nofollow noreferrer">Tutorial: Create ASP.NET MVC localization with language detection</a>

What would be best practice to localize your ASP.NET MVC application?

I would like to cover two situations:

<ul>
<li>one application deployment in IIS which would handle multiple languages</li>
<li>one language/application deployment.</li>
</ul>

In first situation should you go with some kind of view based thing like, ~/View/EN, ~/View/FI, ~/View/SWE or something different?

What about second case, just application based config via Web.config and point these different languages to different URLs?

How to localize ASP.NET MVC application?

本地化ASP.NET MVC应用程序的最佳实践是什么？我想介绍两种情况：IIS中的one应用程序部署，它将处理多语言one语言/应用程序部署。在第一种情况下，你应该使用某种基于视图的东西，比如~/ view /EN，~/View/FI，~/View/SWE或其他东西吗？如果是第二种情况，只是通过Web.config进行基于应用程序的配置，并将这些不同的语言指向不同的URL？

问如何本地化ASP.NET MVC应用程序？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何本地化ASP.NET MVC应用程序？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何本地化ASP.NET MVC应用程序？
EN