PowerShell / PowerShell/vscode-powershell
Suggestion: Include 'Run in External PowerShell Window' by default in debug options
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Hi, all,
Firstly, I love this PowerShell in vscode, thank you for this!
Secondly, I loved PowerGUI while it worked.
Mostly because a lot of the scripting work that I do is very one and done, and I don't need to do a lot of debugging, but the scripts I write are far too long to do freely in a powershell window.
As a result, I LOVED the 'Run in External PowerShell Window' option that PowerGUI supported.
I have found that I can get this functionality back by adding the following Launch Option into my Launch.json file, however, it took far longer than I care to admit to get it working as I wasn't sure about how the launch settings actually worked:
{
"type": "PowerShell",
"request": "launch",
"name": "Run in External PowerShell Window",
"script": "Start-Process",
"args": ["PowerShell.exe -Argumentlist '-NoExit -Executionpolicy Bypass -File ${File}'"],
"cwd": "${File}"
},
Can this please be added as a default Launch option for others who miss this functionality! :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how vscode-powershell contributes default PowerShell launch configurations and compare that behavior with the launch.json snippet in the report. Add the external-window configuration to the defaults, then verify that a new debug configuration exposes it and launches the current file in an external PowerShell window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100