Running a process after creating EXE/DLL

For each EXE/DLL that is created it is possible to run a process - this allows you to do things such as automatically compress the EXE/DLL. Or you could copied the newly create file to another location. The process that is run is fully user configurable through the use of template files. An example template, BUILD.TPL, is provided in the template directory that exists beneath the VOPP3 directory. There are a number of replacement markers that can be used in the templates. At execution time the replacement markers will be replaced by values corresponding to the current EXE/DLL. The replacement markers consist of a percent sign followed by a word. The replacement markers are listed below, with a description following:

Replacement Marker	Description
%FullFile%	The EXE/DLL filename, including path, that is created.
%File%	The filename of the file created, excluding path.
%Ext%	The file extension of the new file.
%Date%	Current date in the format YYYYMMDD.
%Time%	This is the current time as digits. Equivalent to Time24() without the ":". E.g. 223001 is the time 22:30:01
%Hour%	This is the current hour as digits. E.g. 220000 is the time 22:00:00
%Project%	The current project name.
%Drive%	The output drive.
%Path%	The output path (without drive).
%DLLAEF%	Fully specified name of the AEF of prototypes produced by VO when output file is a DLL.

NOTE: Lines within a template file that start with // are considered comment lines and are not written to the batch/cmd file.

Example BUILD.TPL:

// Examples of EXE/DLL compression
//
// pecompact %fullfile% /a /x /j

aspack %fullfile% /Q /R+ /B- /D+ /E-

Normally you want this processing to occur behind the scenes, but sometimes, especially when first setting up a template, it can be useful to see the process running. To do this you can check the Show process checkbox. Also, if you check the Debug process checkbox then the command file VOPPBUILD.BAT, generated from your template will be left on disk in the BIN directory so that you can examine it.

When using System Builder these options are on the main dialog that is displayed. Single App Build also supports the running of a process after creating an EXE/DLL. The options for Single App Build, such as the name of the template to run, are maintained through VOPP Plus!.

System Builder/Single App Build also looks for additional templates having the same name as your original template but ending in BEFORE and/or AFTER. If it finds these templates it will automatically execute them at the start and end of the system build process. So, if your template is named BUILD.TPL, System Builder will also look for BUILD BEFORE.TPL and BUILD AFTER.TPL. If it finds either of these template files it will execute them - the BEFORE template prior to the build and the AFTER template on completion of the build.

In summary:
n No template is executed unless there is a tick in the Run Process box.
n If you specify a template it will be executed for each EXE/DLL created.
n If you have specified a template, BUILD.TPL, and also have another template called BUILD BEFORE.TPL, the "before" template will always be executed at the start of the build process, even if no EXEs/DLLs are produced.
n If you have specified a template, BUILD.TPL, and also have another template called BUILD AFTER.TPL, the "after" template will always be executed at the end of the build process, even if no EXEs/DLLs are produced.
n When using System Builder the process options are specified on the main dialog. When using Single App Build the options are specified in VOPP Plus!.