Are there any performance issues or caveats with resource (.resx) files?

Question

Resource files seem great for localization of labels and messages, but are they perfect?

For example:

1. Is there a better solution if there is a huge amo

Answer 1

Here is my take on resource files:

1. I would assume that if there is a LARGE amount of string, that using a database might be the best method to allow for searching and sorting of the data. It would probably not be too difficult to account for multiple languages in a resource table, and the speed should best fast.

2. I would think that this is a good method for storing static resources, or things that might be changed by a client. As for dynamic resources, it might be better to use a database, either alone, or in conjunction with the file system. I think in the new SQL Server there is a new type that is an optimal hybrid of using a database and the file system.

3. I read in another question (don't know which) that using resource files in an external project is a good practice, because you wouldn't have to recompile an entire project when resources change. Just recompile the resource project. This would also allow for (fairly) easy edits to be made by clients, where they would only need to "source code" for the resource project, and not your other real code (API code, etc.).

4. I have not used resource files enough to make any claims about their reliability, extensibility, or any potential issues that you might have when working with them.