PowerShell / PowerShell/vscode-powershell

PowerShell profile not loaded in temporary PowerShell Integrated Console when `powershell.debugging.createTemporaryIntegratedConsole` is set to true

Open
#1,468 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Debugging Issue-Enhancement
Dominant language
TypeScript
Stars
1.9k
Forks
547
PR merge metrics
No merged PRs in 30d

Description

System Details
  • Operating system name and version: Windows 10 (1803)
PS C:\Users\ohads\Documents\PowerShell> code -v
1.25.1
1dfc5e557209371715f655691b1235b6b26a06be
x64
PS C:\Users\ohads\Documents\PowerShell> $pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1      8      2      0


PS C:\Users\ohads\Documents\PowerShell> code --list-extensions --show-versions
bradygaster.azuretoolsforvscode@1.3.0
codezombiech.gitignore@0.5.0
dbaeumer.vscode-eslint@1.4.12
DotJoshJohnson.xml@2.3.1
DSKWRK.vscode-generate-getter-setter@0.5.0
eg2.tslint@1.0.34
ionutvmi.path-autocomplete@1.12.0
johnpapa.azure-functions-tools@0.3.1
mohsen1.prettify-json@0.0.3
ms-vscode.csharp@1.15.2
ms-vscode.PowerShell@1.8.2
robrodi.language-bond@0.0.1
msazurermtools.azurerm-vscode-tools@0.4.2
pmneo.tsimporter@1.2.14
rbbit.typescript-hero@2.3.2
streetsidesoftware.code-spell-checker@1.6.10
yzane.markdown-pdf@1.2.0
PS C:\Users\ohads\Documents\PowerShell> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.17134.165
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.165
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
Issue Description

The PowerShell terminal and the PowerShell Integrated Console both load PowerShell profiles. However, when setting powershell.debugging.createTemporaryIntegratedConsole to true, profiles are not loaded. Looking at process explorer, I believe powershell.exe is being executed with -NoProfile. This is undocumented, inconsistent, and IMO undesired.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue on Windows with powershell.debugging.createTemporaryIntegratedConsole set to true, then compare profile loading in the PowerShell terminal, regular Integrated Console, and temporary Integrated Console. Inspect the temporary console launch path and verify whether -NoProfile is passed. Done means the temporary console loads profiles consistently with the other consoles.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, typescript
Domain
developer-experience, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.