7.22.0953 |
  
|
7.22.0953 |
|
Released on March 9, 2022
When you deploy QDV you may want to run your own applications before and after effective installation / update of the product.
You can now do this by placing in the installation folder the following files:
runPreUpdate.cmd
runPostUpdate.cmd
when these files are detected (or only one of them), the QDV updater executes the commands being in the files before the installation of the new QDV files (runPreUpdate.cmd) or after the installation of the new files (runPostUpdate.cmd)
This is done whatever 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 QDV 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, QDV 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 QDV 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.
Names WBS_Range_Full and WBS_Range_Item referring to areas in the WBS sheet of the overhead were deleted for a time during the calculation process.
The columns fed by the WBS_to_BOQ_Distribution function were not immediately pushed to the WBS sheet of the overhead so, to have accurate figures in this sheet, it required two selling prices calculations. Now it should need only one.