Tasks

All build tools have a common core: they allow you to model a dependency network. The tool will calculate how to reach the goal specified by executing a set of operations in the correct order. Task-oriented build tools describe the dependency network in terms of a set of tasks. Each task has two essential features: the thing it does and the things it depends on. The tasks should be fully automated and easily invoked individually or as combination.

By convention, tasks are defined in .build\tasks strictly with task name matching file name. A task should be explicitly imported prior invocation.

Example: The default task depends on the Build task, which should be imported

Import-Task Build

Task . Build

Of course a task can be simply defined within the build script itself; in that case there is no need to import it.

Example: The default task depends on the Build task which is defined inline in the build script

Task . Build

Task Build {
    ...
}