Skip to content

preLaunchTask base path not consistent #75084

@synaptek

Description

@synaptek

Issue Type: Bug

This is new in release 1.35.0. When a VSCode workspace is launched from a Windows shortcut it calculates the task path relative to the VSCode install path and when a workspace is loaded manually in a running VSCode instance the path is calculated relative the workspace path.

This now makes it impossible to have a consistent preLaunchTask configuration that works in either case.

VS Code version: Code 1.35.0 (553cfb2, 2019-06-04T01:17:12.481Z)
OS version: Windows_NT x64 10.0.17134

System Info
Item Value
CPUs Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz (20 x 3312)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 127.68GB (120.61GB free)
Process Argv E:\Projects\EdForge\ISP_TUTOR\EFTutorBuilder\TutorBuilder\TutorBuilder.code-workspace
Screen Reader no
VM 50%
Extensions (15)
Extension Author (truncated) Version
vscode-color ans 0.4.5
dart-code Dar 3.1.0
tslint eg2 1.0.43
live-html-previewer hdg 0.3.0
vscode-json5 mrm 1.0.0
cpptools ms- 0.23.1
vscode-code-outline pat 0.2.1
java red 0.46.0
vscodeintellicode Vis 1.1.6
vscode-java-debug vsc 0.19.0
vscode-java-dependency vsc 0.4.0
vscode-java-pack vsc 0.7.1
vscode-java-test vsc 0.17.0
vscode-maven vsc 0.17.0
linecount yyc 0.1.7

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bugtasksTask system issuesverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions