Navigation:  Controlling Upgrades > Pre Update and Post Update Commands

When you deploy QDV7 you may want to run your own applications before and after effective installation / update of the product.

For these purposes, put in the installation folder the following files:

▪runPreUpdate.cmd

▪runPostUpdate.cmd.

When these files are detected (or only one of them), the QDV7 updater executes the commands in the files before the installation of the new QDV7 files (runPreUpdate.cmd) or after the installation of the new files (runPostUpdate.cmd).

This is done regardless of the installation / update method (click-once, web server, setup file).

To be executed, the runPreUpdate.cmd must be installed at the previous update because when QDV7 starts its installation, the new file is not in the installation folder yet. So, the old one, if any is executed. This never occurs with runPostUpdate.cmd because the latter is executed after this installation of the new files.

Because they are CMD files, which could possibly start asynchronous processes, QDV7 has no grasp over the execution of the lines contained in the files. There is no warranty that all lines being in runPreUpdate.cmd are full executed before the installation effectively starts.

When you update QDV7 using the service (which runs usually under administrative permissions), keep in mind that the lines contained in the CMD files are always executed with current-user’s permissions. Otherwise, this would create a significant leak which could be used to possibly harm the computer. So, make sure the lines being in the cmd files do not require elevated permissions.