Jul 18, 2016
The INI file is a basic text file, each line containing a single setting in a key-value format, e.g.
install.group Bvckup 2
For details see here - https://bvckup2.com/support/forum/topic/800.
The following are the settings recognized by the installer:
install.as_admin - if to do machine-wide or user-centric install
install.path - where to put program files
install.group - program group for Start menu, can be blank
install.uninstaller - if to set up the uninstaller
install.app_template - (see below)
install.launch_app - if to launch the app once it's installed
install.launch_app_as_admin - if to launch it elevated
ui.mode - controls the UI mode
ui.console - enables the log console if set to 1
Machine vs user installation
Setting install.as_admin to 1 tells the app to perform a machine-wide installation. More specifically it means that the setup will try and restart with full administrative rights (do the UAC elevation), it will add program group to the All Users' profile and set up the uninstaller entry under HKEY_LOCAL_MACHINE registry branch.
Conversely, setting install.as_admin to 0 will instruct the installer to run as is (with no attempt to elevate itself), the group will be created in the current user's profile and the uninstaller entry will go into HKEY_CURRENT_USER.
If you are to do a user installation into C:\Program Files and without explicitly starting the installer as Administrator, the setup *will* fail.
The uninstaller entry
Setting install.uninstaller to 1 will cause the installer to add a registry entry for Add/Remove Program applet in Windows Control Panel.
You would generally want to add this entry as it is required for the Bvckup 2 update mechanism to work. This is how the setup learns whether the app is installed on the machine and *where* exactly it is.
Populating app's configuration directory
Installer can be told to create and populate app's configuration folder by pointing install.app_template at a folder that contains files and directories to be copied over.
Specified folder must exist, but it may be empty. In this case, the setup will merely create %LocalAppData%\Bvckup2 folder and do nothing else.
Launching the app
If installation completes successfully, the installer can be told to launch the app right away. This is done by setting install.launch_app to 1.
By default, the app will be launched de-elevated, even if the installer itself was launched with full admin rights or if install.as_admin was specified.
Setting install.launch_app_as_admin to 1 will launch it, well, with full admin privileges, triggering an UAC prompt if the installer is running de-elevated.
Specifying the UI mode
Installer supports three UI modes - normal, quiet and hidden.
In normal mode the setup shows the "Installing..." window with the scrolling installation log and the window remains open once the setup is completed.
In quite mode the same window is display, but it is automatically dismissed if the setup completes *successfully*. If the setup fails, then window remains open to allow inspecting installation log
In hidden mode no window is displayed at all. If the setup fails, it fails quietly and the failure is indicated by terminating the process with a non-zero exit code.
In a true spartan fashion, "normal" mode is enabled by setting ui.mode to 1, "quiet" - to 2 and "hidden" - to 3.
Logging & troubleshooting
Setting ui.console to 1 tell the installer to open a console log window and, well, log all sorts of interesting information there. This is primarily meant for debugging scripted installs in hidden UI mode.
Alternatively, the log console can be opened by passing --console argument in the command line:
bvckup2-setup.exe --console --install ...