The .NET Framework makes it easy for developers to localize their applications and controls. The ActiveReports for .NET 3.0 Viewer Control uses the Hub and Spoke model for localizing resources. The hub is the main executing assembly. In our case the application hosts the Viewer Control. The spokes are satellite (resources) DLLs that contain localized resources for the application.
Place the satellite DLLs in subdirectories under the main executing assembly. When the main executing assembly needs a resource, use a ResourceManager object to load the required resource. The ResourceManager uses the thread's CurrentUICulture Property. The common language runtime sets this property or you can set it in code to force a certain UI Culture.
Forcing a certain locale is helpful when you want to test whether your satellite DLL is loading properly. The ResourceManager class uses the CurrentUICulture Property to locate subdirectories that should contain a satellite DLL for the current culture. If no subdirectory exists the ResourceManager uses the resource that is embedded in the assembly.
The Viewer Control is built using the default culture of US English. This is the fallback culture for the Viewer Control. For more detailed information about how the Framework locates satellite DLLs, please refer to the help system in Visual Studio® .NET or the book Developing International Software, 2nd edition by MS Press that contains information on localizing applications using the .NET Framework.