I found that AdvancedInstaller does not actually uses the supplied INI files as-is: it parses their contents and stores that in the aip file.
This results in it not using the latest copy, destroying the markup and possibly even the data. (e.g. custom format or even character-encoding)
I like software being smart, but it should never do unpredictable things like this.
I need AI to just use the latest INI file from disk, that i gave it! How can i disable this "feature" ?
Lets say the newer version of our software uses a file named INITIAL.INI and assume any of the following things about it:
- It now has a new key-value pair.
- It now has a new section without values.
- It now has a new multiline value that is quoted and happens to have a ";" or "#" appear at the start of a line.
- It now uses an extended (non-ASCII) character with a specific encoding (code page 936).
- It is now encrypted as a whole, and therefore actually a binary file.
Simply put; its contents is binary (!) and not ASCII using one of the many INI notations.
I just need the -exact- binary copy of this file installed.
- and therefor -
I do not want the AIP to try and parse / rewrite this INI file at all. Like any EXE file.
I want it to automatically include this newer copy of the file without manually updating it in the AIP file. Like any EXE file.
For me the latter is the actual problem, but i foresee format and encoding issues too with the parsing. No INI format is created equal..
So whenever adding a INI file, i would like to see the option to have this threated as a binary file instead.
When an INI, XML and shortcut file is added to the project an "Import Files" dialog is displayed and asks if you want to add those files in the Windows Installer format or not. If you want to add your INI file as a regular file, you can uncheck it from that list.
Then every time that file is modified, its content will also be updated in the project when at build-time or when the project is reopened.
It seems i misinterpreted that dialog text terminology and quickly clicked OK because i did want to import the files.
I was not aware that importing "in Windows Installer" format meant they got parsed / recreated and such.