vscode: Cannot open Extension Development Window [Windows specific]
Issue Type: Bug
I am unable to open the Extension Development Window in VS Code on Windows. It is stuck on “Building” notification (see the image) on the lower pane and nothing happens even after waiting for a long time.
Steps to Reproduce
- Create the hello world extension template following the steps in Your First Extension guide.
- Press
F5for opening the Extension Development Window.
Extra observations
- I am only experiencing this issue in Windows. I have tried the same on Mac and Linux and in both the cases, it works perfectly fine.
- I have tried compilation commands separately in terminal window, and everything executes properly. The
compilecommand exits after compiling and thewatchcommand watches on file changes and compiles successfully.
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:12:49.994Z) OS version: Windows_NT x64 10.0.18363
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i7-8650U CPU @ 1.90GHz (8 x 2112) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 15.92GB (5.73GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Extensions (18)
| Extension | Author (truncated) | Version |
|---|---|---|
| language-x86-64-assembly | 13x | 2.3.0 |
| code-gnu-global | aus | 0.2.2 |
| vscode-eslint | dba | 2.1.8 |
| githistory | don | 0.6.9 |
| gitlens | eam | 10.2.2 |
| git-project-manager | fel | 1.7.1 |
| guid | kos | 0.0.1 |
| musupport | Mic | 0.0.6 |
| python | ms- | 2020.7.96456 |
| remote-ssh | ms- | 0.51.0 |
| remote-ssh-edit | ms- | 0.51.0 |
| remote-wsl | ms- | 0.44.4 |
| cpptools | ms- | 0.30.0-insiders |
| powershell | ms- | 2020.6.0 |
| vscode-asl | Tho | 1.0.0 |
| vscode-icons | vsc | 10.2.0 |
| edk2-vscode | wal | 1.0.3 |
| markdown-pdf | yza | 1.4.4 |
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 18 (7 by maintainers)
Okay, I found one more observation with this issue.
I normally use Powershell as my default terminal in VSCode. While capturing the output of
preLaunchTaskwith Powershell, I found the following output -Since, I had run
npm run watchseparately in a Powershell terminal window, I knew that this is not the exact output ofnpm run watchand it does spew a lot more logs than simply displaying the message> Executing task: npm run watch <, so I changed the default terminal to Command Prompt, and ran the Build task again. This time, the Extension development window did open and I received the following output -But I am not sure what to make of this - whether it is a problem with Powershell or integration of Powershell with VSCode. I normally use a custom profile in Powershell, but I have also tried without using any custom profile and I am still not seeing the issue getting reproduced.
@alexr00 I found #103390 through #104157, it solved my problem very well, thank you for your help.
@alexr00 This worked! Thank you for your help. 😄
@unkemptArc99 the task system works by passing the
-Commandargument to your chosen shell. In this case, since you have a bunch ofshellArgsset, that doesn’t work. You should be able to solve this by simply setting"terminal.integrated.automationShell.windows"to the shell of your choice. Can you try setting that setting to powershell and see if it solves your problem?I also encountered this problem today. Reproduction steps are the same as you
VS Code version: Code 1.47.3 (91899dc, 2020-07-23T13:12:49.994Z) OS version: Windows 10 1903