Collapse All Expand All

ActiveReports uses the Hub and Spoke model for localizing resources. The hub is the main executing assembly, for example, the Viewer Control, ActiveReports.Viewer6.dll.

The spokes are the satellite DLLs that contain localized resources for the application, for example, ActiveReports.Viewer6.resources.dll.

The Localization folder, C:\Program Files\GrapeCity\ActiveReports 6\Localization (on a 64-bit Windows operating system, the localization folder is C:\Program Files (x86)\GrapeCity\ActiveReports 6\Localization), contains everything you need to localize all of your ActiveReports components.

Within that folder, each component of ActiveReports that you can localize, 14 in all, has two files:

• *.bat Set the culture to which you want to localize.
• *.zip Change the strings in the resource files (*.resx) it contains.

There is one application in the folder: NameCompleter.exe When you run your bat file after changing it to your culture, it runs this application to create a SatelliteAssembly folder with a language subfolder containing the localized ActiveReports.AssemblyName.resources.dll file.

Place the culture subdirectories containing the satellite assemblies in the folder that contains your main executing assembly.

When the main executing assembly needs a resource, it uses a ResourceManager object to load the required resource. The ResourceManager uses the thread's CurrentUICulture property.

The common language runtime sets the CurrentUICulture property or you can set it in code to force a certain UI Culture to test whether your satellite DLL is loading properly. The ResourceManager class uses the CurrentUICulture Property to locate subdirectories that contain a satellite DLL for the current culture. If no subdirectory exists, the ResourceManager uses the resource that is embedded in the assembly. US English is the default culture for ActiveReports.