Editing installation scripts

When editing installation scripts for VBScript-based packages, the default editor is launched with the full path of the script, which is located inside the Package in the Scripts folder., like this;

For PowerPacks, however, the installation scripts are located in the SQL database (in the JOB table), and when you right-click on a PowerPack and then select ‘Edit installation script’, the script is saved in a temporary folder, and the PowerPack Editor is then launched with the temporary script.

The Ci Console will monitor the file, and track any changes when you save them. To make sure that the changes made were deliberate, the Change log dialog is shown to let you add a reason for the edit.

When you click Ok, the script is saved to the database.

Having the installation scripts in the database offers the ability to edit the scripts and install the package without starting an ‘Update Now’ synchronization action to other containers. This means that changes to the installation script of a PowerPack will have immediate consequences for anyone installing the package on any client connected to any FrontEnd in the whole installation. Even for clients that end up receiving the CapaInstaller.kit file from its own file cache, a nearby peer (FileSharing), or a Distribution Server, the Installation/uninstallation script is fetched from the database.