使用SQL本地化，而不是ASP.NET RESX文件 [英] Using SQL for localization instead of RESX files in ASP.NET

问题描述

我想发展以下，但不知道如果它已经存在在那里的：

I'm thinking of developing the following but wondering if it already exists out there:

我需要为一个asp.net网站的分配和管理本地化的文本值，而不是使用RESX文件的基于SQL的解决方案。这有助于维护网站上的文字，而不必每次需要更新把它记下来进行部署。

I need a SQL based solution for assigning and managing localization text values for an asp.net site instead of using RESX files. This helps maintain text on the site without having to take it down for deployment whenever an update is required.

感谢。

推荐答案

我们居然跑到了这条道路，并结束了一个真的很慢的网站 - 剥开基于SQL的转换机制，并使用ASP.NET资源给了我们一个显著的性能提升。所以我不能真的建议你这样做同样的事情......（是 - 我们缓存和优化吞吐量和一切 - 以及基于SQL的东西仍然显著慢）。

We actually went down that path, and ended up with a really really slow web site - ripping out the SQL-based translation mechanism and using the ASP.NET resources gave us a significant performance boost. So I can't really recommend you do that same thing.... (and yes - we were caching and optimizing for throughput and everything - and the SQL based stuff was still significantly slower).

您得到你所支付的 - 基于SQL的方法是在能够对飞翻译，并修复错别字之类的东西方面更加灵活。但最终，在我们的应用程序（Web表单，.NET 2.0在那个时候），利用的资源被证明是去是唯一可行的办法。

You get what you pay for - the SQL based approach was more flexible in terms of being able to "translate" on the fly, and fix typos and stuff. But in the end, in our app (Webforms, .NET 2.0 at that time), using resources proved to be the only viable way to go.

这篇关于使用SQL本地化，而不是ASP.NET RESX文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！