At my office, we have had a long-standing debate about Localization/Globalization and how to handle it. One side pushes for the Resource (.resx) file route built in to ASP.NET, one side pushes for a database driven solution. A third group believes in rolling a custom solution.

Of course, each method has its own unique benefits and disadvantages - and we've discussed it over and over, without ever coming to a real consensus.

So, I pose it to the community: in your experience, which method provides the best mix of the following as the application grows:

  1. Maintainability
  2. Extensibility
  3. Performance / Scalability

In addition to just advice, we'd also be interested in any open source projects which might help to simplify the question, as well. Thanks!

asp.net localization globalization resx
Edit
Report