I've encountered the following issue; I use AI to write a registry value of type REG_BINARY using an installer Property. The property value is set to 01000000. The writing of this registry value works well on clean installs where the value does not exist. When upgrading an existing installation, I add an Application Search for this value and retrieve the raw value to set to the same installer property if it exists. When the Application Search retrieves this raw value, it retrieves it as #x01000000. Now when AI a attempts to write this value, it writes it as #x#x01000000 which causes it to raise an error and fail to write the value.
Thanks. I understand the intended functionality of the Search, but to describe the retrieved value as 'Raw' is misleading; it's clearly formatted by AI. Perhaps you could consider an option to retrieve values as Formatted (like they are currently) or Raw (unedited by AI) so as to avoid this issue.
I found the linked 'how to' article convoluted. To resolve the issue, I simply created a Win32 DLL that runs after the Search and strips the #x from REG_BINARY values. So much cleaner and simpler.
These are predefined Windows Installer searches, not custom made by Advanced Installer. Our application only presents you with the possibility to easily add and configure them.
My colleague meant that Advanced Installer is built on the Windows Installer technology, thus limited in some areas by Microsoft's predefined standards.
When adding the registry in the Registry page, Advanced Installer automatically sets the .MSI table entries responsible for writing the registry values, according with the Windows Installer standards. All the .AIP settings are included in the result .MSI at build time. In the end, when running the .MSI on the target machine, the registry entries get written by the Windows Installer process.
FOLLOW US
Get the latest news in Application Packaging