本地化与ASP.NET MVC 2.0 中的全球化
我知道已经有几篇关于这个主题的帖子了，但我仍然很困惑。
http://www.codeproject.com/KB/aspnet/Localizing_ASP_NET_MVC .aspx?msg=3189952#xx3189952xx
这看起来很简单，但有些人说它没有使用 App_LocalResources 文件夹。
所以我不确定这些文件夹之间有什么区别以及为什么您应该使用这两个文件夹。
另一方面，这篇文章看起来很长，并且有相当多的代码来改变语言。
http://adamyan.blogspot.com/2010/02 /aspnet-mvc-2-localization-complete.html
所以我不确定哪个更好。第一个是我期望的代码，但我不确定是否是因为您让用户选择他们的语言（而不是使用自动或硬编码值），导致代码膨胀并且太长。
I know there have been a couple postings on this topic already but I am still confused.
http://www.codeproject.com/KB/aspnet/Localizing_ASP_NET_MVC.aspx?msg=3189952#xx3189952xx
This one seems pretty simple but some people stated that it does not make use of the App_LocalResources folder.
So I am not sure what the difference between these folders are and why you should be using both.
On the flip side this posting seems pretty long and has quite a bit of code to make it change languages.
http://adamyan.blogspot.com/2010/02/aspnet-mvc-2-localization-complete.html
So I am not sure which one is better. The first one is what I expected the code to be but I am not sure if it is because you given the user the choice to choose their language(opposed to using auto or hard coded value) that the code just swells up and is so long.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
两种方法基本相同，因为资源文件生成带有返回字符串的属性的公共类。
第一个对所有字符串使用一个全局资源 (
App_GlobalResources)，第二个解释如何为不同视图分离资源。在我看来，全局资源对于 MVC 应用程序来说更好，因为您可以在模型和视图中重用它们，但是 YMMV。
Both approaches are basically the same, since the resource files generate public classes with properties returning the strings.
The first use one global resource for all the strings (
App_GlobalResources), and the second one explains how do separate the resource for different views.In my opinion a global resources are better for MVC apps since you can reuse them in the model and in the views, but YMMV.