We are looking at how to best localize the static content of a packed ASP.NET app. The current idea is to use resource files and satellite assemblies to localize the texts in the web pages.
Most examples seem to use one big resource file for the app and manually create an ID for text strings in the resx file. Then this is wired together. Either explicitly in code by calling rm.GetString(ID) or by creating a property on the control for specifying the ID and using a framework class or inherited control that read from the resource manger.
This all seems a bit tedious.
We have looked at a tool called ASP.NET Localizer (http://www.winformreports.co.uk/features_loc.htm). It has a control you can drop onto the form. It then stores all texts and other translatable properties of the built in web controls in the resx file created for the ASP.NET page. If you change the language in the designer, it creates a new resx file for that language and stores all properties you translate in the appropriate resx file. At runtime it reads the properties for the controls from the resx file. Seems pretty cool. Thoughts?