VSCode Debugging with Arguments

[spozner]

Please update the debugging options in VSCode to allow for either:

• keeping the last 10 unique arguments passed to the current script

• set it up so we can launch a Powershell function directly to debug execution or extend debugging.

Ultimately, when launching a script, I'd like to be able to select the parameters available when Launching the script (Easily exposed using the Show-Command ${file} -Passthru command and arguments, or select them from a last used set of arguments for that particular file. I've written code to do this for the PSISE and it worked great but, I'm finding the debugging interface in VSCode lacking and would like to extend it.

[TylerLeonhardt]

set it up so we can launch a Powershell function directly to debug execution or extend debugging.

We supply a debug configuration called "PowerShell: Launch Script"

vscode-powershell/package.json

Lines 522 to 530 in ee5521f

	"label": "PowerShell: Launch Script",
	"description": "Launch and debug the specified file or command",
	"body": {
	"name": "PowerShell Launch Script",
	"type": "PowerShell",
	"request": "launch",
	"script": "^\"enter path or command to execute e.g.: \\${workspaceFolder}/src/foo.ps1 or Invoke-Pester\"",
	"cwd": "^\"\\${workspaceFolder}\""
	}

If you put your function... or really any script in there. That should work.

[TylerLeonhardt]

keeping the last 10 unique arguments passed to the current script

I thought we had an issue about this but I guess not. I think it's a reasonable request.

[rkeithhill]

There is a request for this somewhere. What I remember is that the VSCode API did not support an input box (at the time) that allowed you to either select from a list OR enter arbitrary text.

[TylerLeonhardt]

@rkeithhill I feel like this might be possible now

[spozner]

@rkeithhill Were you able to find it? Seems like an easy ask to have it remember the last x number of commands used when launching the active script...
@TylerLeonhardt Thanks for pointing me to that, I was able to use my old PSISE code to launch the active script. I'm having a small problem setting up the hotkey for it as even F5 seems to default to that entry. I wanted to create a new hotkey that enters debugging but uses my custom function which tracks the last 10 unique parameters used based on the script name.

The Launch.json:

"configurations": [
{
"name": "PowerShell: Launch Current File",
"type": "PowerShell",
"request": "launch",
"script": "${file}",
"cwd": "${file}"
},
{
"name": "PowerShell Launch GetParameters Script",
"type": "PowerShell",
"request": "launch",
"script": "Get-VsCodeScriptParameters",
"cwd": "${file}"
},
]

The VSCode Module I load defines the function and also loads the command to be executed in the editor. I just cannot figure out why I can't use F5 for one and CTRL+ALT+F5 for gathering parameters. Any insight would be helpful.

[rkeithhill]

@TylerLeonhardt What is the new API? I was just using a new extension the other day and figured out this is what they were doing to get around the lack of this type of control:

BTW this ^^ confused the heck out of me because I kept typing in a new regex and it wouldn't take it. Turns out this is a pick list. You either have to pick a previously entered regex, that's in the list, OR click on New pattern... to get to the second level, text input box shown below:

[TylerLeonhardt]

@rkeithhill yeah I think I've seen similar experiences and that's what I was referring to wrt an "API". That is probably still better then what we have... but I'll let @spozner chime in on that to see.