Alejandro Quiroga Alsina wrote @ Sebastian: I did look thoroughly ;-) And when I use the Resource Files Verifier it does not inform any "obsolete entries" for the SharedResources.resx file. Question: ¿How does the Resource Verifier check if an entry is obsolete?

Hi Alejandro,

while agreeing to all your other statements I'll answer your question: The Resource verifier is a simple tool, mainly designed to assist translators. It is checking for duplicate entries in the base resource ("en-US") and comparing other languages to it. AFAIK there is no option to evaluate, whether a resource key is used in fact, since this can be done using the resource key in a control placed on an ascx file or in code using the GetString option with a concatinated key. Module developers shall use the ShowMissingKeys option in web.config file to verify that all text is derived from the resource files, but besides there is no support, especially for  orphaned keys (e.g. Repository has 3 orphaned resource files, I am requesting to remove for about 2 years now.)

Hi Sebastian!

Thank you very much for your update on this issue! :-)

And BTW, contratulations on your extremely useful moderation/participation on these forums. You are the best.

Saludos!

Alejandro.

Alejandro Quiroga Alsina wrote @ Sebastian: I did look thoroughly ;-) And when I use the Resource Files Verifier it does not inform any "obsolete entries" for the SharedResources.resx file. Question: ¿How does the Resource Verifier check if an entry is obsolete?

sorry, I overlooked this question. The resource verifier does NOT compare default language resource file with code - this is simply impossible, since there are numerous ways to call the resource key. If a developer removes the need for a resource key, he is responsible to remove it from the resource file as well, the resource verifier will list tranlated files to have obsolete entries, which will be removed automatically by the language editor when editing.