At the moment, all of our localised texts are stored in resource files and then referenced using <% $Resouces:Something %>. Unfortunatly this method is not scaling too well, were getting lots of diff problems & the files are becoming rather big. Does anyone know of a better solution for localisation? Or is resource file's all I've got in ASP.NET?
+2
A:
You can use a custom resource provider to store localization data in a something other than a resx file. Here's a good article by Rick Strahl where he demonstrates how to store resource information in a database.
Creating a Data Driven ASP.NET Localization Resource Provider and Editor
Here's an MSDN article on creating your own custom resource providers, it also includes a section on how to use a custom resource provider to access content from a database.
Phaedrus
2009-02-09 14:24:55
That's pretty sweet. I wish I would have known about that a year ago.
Greg
2009-02-09 14:31:18