Create a custom Setup.msi file
- Last UpdatedMar 26, 2025
- 2 minute read
- HMI and SCADA
- System Platform
- Historian 2026
The AVEVA Historian Client Language Toolkit includes a Windows Installer XML (WiX) template that allows you to generate a localized installer package of resource assemblies for AVEVA Historian Client. The package itself is in the form of a .msi file.
The template, named config.wxi, provides the framework for localizing AVEVA Historian Client into the language you specify.
To generate a localized installer package
-
Open the "Config.wxi" template in Visual Studio.
-
Provide values for the fields listed.
Tip: From the command prompt, you can run the Guidgen tool that comes with Visual Studio to generate GUIDs. When the tool opens, select the Registry format and generate the new GUID for the resources.
Follow these guidelines:
-
Use the Registry format for GUIDs.
-
UpgradeCode is set once and never changed for the life of localized installation.
-
ProductCode and PackageCode are changed once per major release.
-
Component GUIDs are also set for the life of the localized installation.

-
-
From the Solution Explorer pane in Visual Studio, right-click Setup.msi and select Build.
This compiles the project.
-
At the bottom of the Visual Studio window, click the Output tab to confirm that the project was compiled without errors.
-
Right-click the Config.wxi tab and select Open Containing Folder to see the output.
-
Navigate to the bin\Release subfolder to find the newly compiled Setup.msi file.
When this file is installed on a computer, the user will see a subfolder for the localized language under the ArchestrA folder. For example, if you just created a Setup.msi for Russian, and if the ArchestrA folder was in its default location, the user would see this:
