| What is a kit command | ![]() |
| Program } Commandline } WorkingDir |
| Program parameter |
|
| Executable - filename or instruction to run, which is divided into the token and program string. Token Program Or TokenProgram The token is one or more characters at the start of the parameter that defines the commands purpose, for example to run notepad without waiting:
There are three types or groups of token, and the expected content of the program string changes for each: Runners For controlling the runtime of an executed program. When no token is specified AC waits for the program to finish before proceeding. Expects: A program name or path, if not specified AC assumes the program to be the windows command interpreter cmd.exe Wrappers Advanced commands that take user input via a shell dialog and places it within a runner or booty command before execution. Expects: The token and program string of the embedded command plus a comma delimited set of wrapper parameters. Booty A catch all group of internal commands. Expects: A command specific string, some use it some don't. |
| Commandline parameter |
| Arguments to be passed to the program being executed, other types of commands may use this for additional configuration. |
| Working directory parameter |
| The working directory of the program being executed, only runner commands use this. |
| Where you will encounter kit commands |
| During standalone creation |
||
The kit build override option A3C_KBO takes a normal command:
During the 'Execute' phases A3C_PBE and when using its gui element menu A3C_PBE_MNU an extended kit command format is used:
|