Collapse All Expand All

To localize ActiveReports Resources

1. In Windows Explorer, navigate to C:\Program Files\GrapeCity\ActiveReports 6\Localization (on a 64-bit Windows operating system, navigate to C:\Program Files (x86)\GrapeCity\ActiveReports 6\Localization).
2. Edit the *.bat files of any assemblies that you want to localize:
   1. Right-click the *.bat file and select Edit.
   2. Change the culture in the line set Culture="en-Us" to the culture that you want to use. For your convenience, here is a list of predefined .NET Cultures.
   3. Ensure that the ProgamFilesDDPath is correct.

      Caution: Do not change the ProjectName, dllName, msDir, or BaseNamespace.

   4. Save and close the *.bat file.
3. Change strings in the resource files:
   1. Double-click the *.zip file of the assembly that you want to localize to open it.
   2. Extract all of the files to C:\Program Files\GrapeCity\ActiveReports 6\Localization (on a 64-bit Windows operating system, extract the files to C:\Program Files (x86)\GrapeCity\ActiveReports 6\Localization). A subfolder with the same name as the zip file is created.
   3. In the new folder's Res subfolder, open each of the *.resx files and change the strings as needed.
   4. If you want to change any of the images, rename your localized images to the names of the ones in the Res\Resources subfolder and replace them with your localized images.
4. Back in the main Localization folder, double-click the *.bat file to run it. The NameCompleter.exe application runs, and creates:
   • A SatelliteAssembly folder inside the new folder.
   • A language subfolder with the same name as the culture you set in the *.bat file inside the SatelliteAssemby folder.
   • A localized ActiveReports.AssemblyName.resources.dll file inside the language subfolder.
5. Copy the language subfolder and paste it into the Debug folder of your application.

   Note: If you want to put your localization in the Global Assembly Cache (GAC), you must first send the localized ActiveReports.AssemblyName.resources.dll file to GrapeCity and get it signed. Then you can drag the language subfolder with the signed dll file into C:\WINDOWS\ASSEMBLY.

To test your localized application on a machine that does not share the culture of the localized dll

1. Add the following code in the form's constructor just before the InitializeComponent method is called.
2. Replace the "ja" in the example code with the culture specified in the *.bat file.

To write the code in Visual Basic.NET

To write the code in C#