We are working on an installer. A colleague of mine added a couple of windows for the custom installation and while he was debugging it, he saw that the XML files that are generated by AI, are not resolving the [ComputerName] property in the typical installation. The XML files are placed in a folder that is configured to place it's content in the parent folder.
All the other properties are working just fine, except [ComputerName]
I'm not sure why you encounter this behavior, I tested it, but it worked well to me. Can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them?
I found that there are two XML files with the same name in your project and they are installed in the same parent folder conditioned by two different properties (InstallModeTypical and InstallModeCustom).
However, the log shows that both properties are set during the installation, which means that both conditions are true and both XML files are installed in the same location. Since they have the same name and they are installed in the same folder, one is replacing the other.
It seems that the XML file created for "Custom" installation mode is replacing the XML file created for "Typical" installation mode. That XML file contains a property called [ESB_INVOKE_ADRESS] and the log shows that this property is not created and set during the installation, hence the XML file created contains no value where it should contain the value of the [ESB_INVOKE_ADRESS] property.
First of all I suggest you to set correct conditions for these XML files and also you can test the above assumptions by setting a default value for the [ESB_INVOKE_ADRESS] property.