Checking your module for localization

DotNetNuke 3.0 introduced a localization framework to better serve international users.  This framework has undergone several small updates in the last year to make the framework easier to use and to help developers test their modules.

While working on the DotNetNuke Module Review program, we were forced to figure out how to determine if a module is completely localized.  After looking at various options, the easiest solution turned out to be both simple and elegant.  To conduct the test, make sure the AppSettings/ShowMissingKeys in web.config is set to true.  Then just rename the App_GlobalResources, the Controls/App_LocalResources and the module's App_LocalResources folders.  As you can see, it becomes readily apparent which strings are localized and which are not.

After renaming the folders