Application Path Settings

These settings allow you to specify custom executable paths for build tools and task runners supported by the extension. On all platforms, ~/ in a path is automatically expanded to the user’s home directory. On Windows, if a path ends with the bare executable name (e.g. ant, not ant.exe), the appropriate extension (.exe, .bat, .cmd) is appended automatically.

Some tools have dedicated sub-pages with additional tool-specific settings:

Sub-section Description
Act Run GitHub Actions locally with act
Ant Ant build tool and ANSICON settings
CircleCI CLI Run CircleCI jobs locally with circleci
CMake CMake build system settings

Table of Contents

  1. workspaceTasks.applicationPath.ansicon
  2. workspaceTasks.applicationPath.cargo
  3. workspaceTasks.applicationPath.cargo-make
  4. workspaceTasks.applicationPath.composer
  5. workspaceTasks.applicationPath.deno
  6. workspaceTasks.applicationPath.gradle
  7. workspaceTasks.applicationPath.just
  8. workspaceTasks.applicationPath.make
  9. workspaceTasks.applicationPath.maven
  10. workspaceTasks.applicationPath.msbuild
  11. workspaceTasks.applicationPath.pipenv
  12. workspaceTasks.applicationPath.poe
  13. workspaceTasks.applicationPath.poetry
  14. workspaceTasks.applicationPath.rake
  15. workspaceTasks.applicationPath.taskfile

workspaceTasks.applicationPath.ansicon

   
Type: string
Default: "ansicon.exe"
Scope: resource

Path to the ANSICON executable used to provide colored output for Ant tasks in the Windows terminal.

Example:

{
  "workspaceTasks.applicationPath.ansicon": "ansicon.exe"
}

Screenshot - Ansicon Path

workspaceTasks.applicationPath.cargo

   
Type: string
Default: "cargo"
Scope: resource

Path to the Cargo executable (Rust package manager and build tool). On Windows, .exe is appended automatically when the path ends with cargo.

Example:

{
  "workspaceTasks.applicationPath.cargo": "cargo"
}

workspaceTasks.applicationPath.cargo-make

   
Type: string
Default: "cargo-make"
Scope: resource

Path to the cargo-make task runner. On Windows, .exe is appended automatically when the path ends with cargo-make.

Example:

{
  "workspaceTasks.applicationPath.cargo-make": "cargo-make"
}

workspaceTasks.applicationPath.composer

   
Type: string
Default: "composer"
Scope: resource

Path to the Composer PHP package manager executable. On Windows, .bat is appended automatically when the path ends with composer.

Example:

{
  "workspaceTasks.applicationPath.composer": "composer"
}

Screenshot - Composer Path

workspaceTasks.applicationPath.deno

   
Type: string
Default: "~/.deno/bin/deno"
Scope: resource

Path to the Deno runtime executable. On Windows, .exe is appended automatically when the path ends with deno.

Example:

{
  "workspaceTasks.applicationPath.deno": "~/.deno/bin/deno"
}

Screenshot - Deno Path

workspaceTasks.applicationPath.gradle

   
Type: string
Default: "gradlew"
Scope: resource

Path to the Gradle wrapper or executable. On Windows, .bat is appended automatically when the path ends with gradle.

Example:

{
  "workspaceTasks.applicationPath.gradle": "gradlew"
}

Screenshot - Gradle Path

workspaceTasks.applicationPath.just

   
Type: string
Default: "just"
Scope: resource

Path to the Just command runner. On Windows, .exe is appended automatically when the path ends with just.

Example:

{
  "workspaceTasks.applicationPath.just": "just"
}

Screenshot - Just Path

workspaceTasks.applicationPath.make

   
Type: string
Default: "make"
Scope: resource

Path to the Make executable. On Windows, .exe is appended automatically when the path ends with make.

Example:

{
  "workspaceTasks.applicationPath.make": "make"
}

Screenshot - Make Path

workspaceTasks.applicationPath.maven

   
Type: string
Default: "mvn"
Scope: resource

Path to the Maven executable. On Windows, .cmd is appended automatically when the path ends with mvn.

Example:

{
  "workspaceTasks.applicationPath.maven": "mvn"
}

Screenshot - Maven Path

workspaceTasks.applicationPath.msbuild

   
Type: string
Default: "msbuild"
Scope: resource

Path to the MSBuild executable. On Windows, .exe is appended automatically when the path ends with msbuild.

Example:

{
  "workspaceTasks.applicationPath.msbuild": "msbuild"
}

Screenshot - MSBuild Path

workspaceTasks.applicationPath.pipenv

   
Type: string
Default: "pipenv"
Scope: resource

Path to the Pipenv Python environment manager. On Windows, .exe is appended automatically when the path ends with pipenv.

Example:

{
  "workspaceTasks.applicationPath.pipenv": "pipenv"
}

Screenshot - Pipenv Path

workspaceTasks.applicationPath.poe

   
Type: string
Default: "poe"
Scope: resource

Path to the Poe the Poet task runner for Python projects. On Windows, .exe is appended automatically when the path ends with poe.

Example:

{
  "workspaceTasks.applicationPath.poe": "poe"
}

workspaceTasks.applicationPath.poetry

   
Type: string
Default: "poetry"
Scope: resource

Path to the Poetry Python dependency and packaging tool. On Windows, .exe is appended automatically when the path ends with poetry.

Example:

{
  "workspaceTasks.applicationPath.poetry": "poetry"
}

workspaceTasks.applicationPath.rake

   
Type: string
Default: "rake"
Scope: resource

Path to the Rake Ruby build tool. On Windows, .bat is appended automatically when the path ends with rake.

Example:

{
  "workspaceTasks.applicationPath.rake": "rake"
}

workspaceTasks.applicationPath.taskfile

   
Type: string
Default: "task"
Scope: resource

Path to the Task (go-task) executable. On Windows, .exe is appended automatically when the path ends with task.

Example:

{
  "workspaceTasks.applicationPath.taskfile": "task"
}

Custom path example:

{
  "workspaceTasks.applicationPath.taskfile": "~/bin/task"
}

Table of contents