Hello everyone.
I have put together a list of requirements for our product installer, and for some of the items I am looking for reliable solutions:
Requirements:
1) The folder structure and the contents (files and subfolders) to be put into the installer are provided in a specific folder in the filesystem. This folder is being assembled by a script which runs before AI is being run.
1) Two configurations of the software exist, each having different contents in subfolder "db" (except that the db\data dir exists in both), each will result in a different installer:
Configuration 1:
...
APPDIR\bin\db\abc
APPDIR\bin\db\data\ABC1
...
Configuration 2:
...
APPDIR\bin\db\xyz
APPDIR\bin\db\data\XYZ1
...
2) The folder APPDIR\bin\db\data\ must never be touched on updates.
3) The folder APPDIR\bin\db\data\ is going to be extremely large, copying this folder is never an option.
4) The folder APPDIR\bin\db\data\ must be removed at full uninstallation.
5) Files must always be overwritten (except for 2)) file modification dates or version information must be irrelevant.
6) Low/zero maintenance of the installation project when adding, renaming or removing files/folders from the installer ("Files and Folders").
This excludes:
- Configuring individual file attributes manually (error prone: forget to configure -> installer broken).
- Manually adding, renaming or removing files/folders in the installer project (error prone: forget to add, rename, remove in installer project -> installer broken).
However, lightweight scripting (of AdvancedInstaller.com) and lightweight scripted modification of the installer project file are acceptable.
7) Directly after the installer ran through without user visible error (be it for update or new installation) no files or folders may be missing (not the case with file versioning and pending file operations).
8.) If errors occurr a rollback must be performed. In case of new installations the files already placed on disk must be removed (not the case with an ErrorMessage custom action) and the user be informed.
To solve 2) we so far resorted to renaming the data folder to have it under APPDIR\bin\db\data.keep in the installer. Then, after fresh installation, the folder would be renamed to APPDIR\bin\db\data in the installation directory via a custom action. This approach turned out to be problematic because the "data.keep" folder (or any of the files contained in it) can be (and actually were at least once) locked (possibly by anti-virus) for at least 5 seconds (after which our custom action silently gives up), leaving a broken installation behind. (At an update the newly placed "keep.data" folder would not be renamed, but deleted instead.)
To get around the problem of "data.keep" being locked when trying to rename I considered adding the files in that folder into the MoveFile table at runtime in a custom action script, but here lack of documentation seems the problem.
I hope I didn't leave to many things out and that these requirements can be satisfied somehow, with reasonable effort.
Thanks for any answers in advance.
With best regards
Clemens Anhuth
FOLLOW US
Get the latest news in Application Packaging