In the traditional GetString approach or other equivalents, risks exist that the accesses to resource text are uncontrollable. This is especially true in large software projects or team development, where it is not possible to make sure all resource text acquisitions are correct and available. For example, there could be spelling errors and can be chaos resulted from multiple revisions on resource files.
Based on our experience, by using the traditional resource text acquisition methods, with simply a few hundred resource strings there could be catastrophic loss of control, inability to maintain or check one by one, and therefore extra and high costs to the project.
Think about the following:
Spelling errors occur when developers get resources.
When the resource files are modified, the original resource file identifiers are modified but not synchronized to other parts of the program.
When the resource files are modified, the original resource entries are deleted by mistake, or some entries mistaken as no longer in use, but actually still in need somewhere are deleted.
Cannot know the usage of a specific resource text entry: whether it is in use; whether it is used in multiple places.
When adding language resources, it is hard to guarantee the synchronization of different language resources, especially when there are large number of resources and revisions.
These problems are even more serious with more project participants. You need a reliable and controllable approach to guarantee the quality of your projects.
SailingEase .NET Resources Toolis designed to solve the above problems.