Re: Whether to use .NET localization support or roll our own...

You've got better tool support for resource assemblies.

It depends on what value-added you get out of putting your resources in a
database.  I've worked on projects that do this and one of the issues was
availability of the resources.  They distributed the database, so they
effectively had distributed resources.  This meant that if the database
wasn't accessible you couldn't display any text to the user.

The other issue that came up, at least with these projects, is multi-lingual
text.  Where does that get stored?  With a DB implementation you invariably
have to have localizable text in at least two places; which is
a maintenance nightmare.

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives