In the Visual Studio project file you will find new PreLink, PreBuild and PostBuild commands which are responsible for the desired result: The split is driven by the rc.config xml file, which you will find in the RINT folder. In this example the split is made by the muirct tool just after the build process. In the API DevKit you will find one example (DG_Test) on how to build the Add-On to achieve the result corresponding to the MUI resource technology. The split is driven by the resource configuration xml file in both cases.

by using the resource compiler to split the resources before the linkage of the final binaries.

by using the muirct tool on the final executable binary to split it afterwards.There are two ways to achieve the separation during the build process: The loaded language depends on the system and User settings. The language specific “.mui” files are handled and loaded by the system automatically. This file should be placed in a folder with the name of an appropriate language ID and this folder should be located next to the belonging language neutral executable file. The language specific resources are separated to a file with “.mui” extension. The basic benefit of MUI Resource Technology is the separation of the executable code and language neutral resources from the language specific resources. The usage of this resource technology is not obligatory. Now on Windows platform MUI Resource Technology have been introduced into ARCHICAD 22 which is available for Add-On developers too. That prevented to create multi-language Add-Ons, the Add-On developers have to build separate Add-On files for each language.

Before ARCHICAD 22 an ARCHICAD Add-On was a single “.apx” executable file which contained both executable code and resources.

Archicad macos