Skip to content

Ignoring "Command Prompt" in terminal.integrated.defaultProfile.windows during build. #132766

@mcheedle

Description

@mcheedle

Issue Type: Bug

VS Code is no longer recognizing "terminal.integrated.defaultProfile.windows": "Command Prompt" when I run a build while building an Azure Function dotnet core 3.1 project.

As a workaround I'm setting "terminal.integrated.automationShell.windows": "C:\Windows\System32\cmd.exe". This started happening this week after an update.

"Command Prompt" = "C:\Windows\System32\cmd.exe" in profiles.

VS Code version: Code 1.60.0 (e7d7e9a, 2021-09-01T10:41:52.311Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

Extensions (27)
Extension Author (truncated) Version
vscode-sql-formatter adp 1.4.4
azurite Azu 3.14.2
vscode-markdownlint Dav 0.43.2
vscode-diff fab 1.4.2
code-runner for 0.11.5
csharpextensions jch 1.3.1
vscode-nuget-package-manager jmr 1.1.6
minifyall jos 2.9.2
json2csv kha 0.0.1
l13-diff L13 1.0.3
vscode-azurefunctions ms- 1.5.0
vscode-azureresourcegroups ms- 0.4.0
vscode-azurestorage ms- 0.12.1
vscode-asa ms- 1.0.1
csharp ms- 1.23.15
vscode-dotnet-runtime ms- 1.2.0
mssql ms- 1.10.1
python ms- 2021.9.1191016588
vscode-pylance ms- 2021.9.1
jupyter ms- 2021.8.2041215044
jupyter-keymap ms- 1.0.0
azure-account ms- 0.9.8
notepadplusplus-keybindings ms- 1.0.7
azurerm-vscode-tools msa 0.15.2
elastic ria 0.13.3
azure-event-hub-explorer Sum 0.1.1
change-case wma 1.0.0

Metadata

Metadata

Assignees

Labels

*duplicateIssue identified as a duplicate of another issue(s)

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions