ConvertTo-SecureString hangs PowerShell host when run in the VS Code debugger

If you run the below code without using Wait-Debugger then it will run correctly without issue:

param($Request, $TriggerMetadata)

Wait-Debugger
$EncryptString = "eamon"
Write-Output $EncryptString

$TestSecure = ConvertTo-SecureString -String $EncryptString -AsPlainText -Force

$TestSecure

If you run it with Wait-Debugger enabled, it will not complete and hang in VSCode.

[TylerLeonhardt]

with “no configurations”

This just means it launches the script and runs it in the Integrated Console below with debugging.

From my experience, this issue only serviced in the attach debugging scenario.

[invisibleaxm]

One more piece of info to expand on the example provided by @ZanattaMichael as I think this could be related to assignment of a secure string vs the actual converto-securestring cmdlet ? Take for example the following slightly modified scenarios which are both working inside azure functions / debugged locally:

This example has an error (empty string), however the debugger is able to continue onto next line (it just complains about the empty string)…

Wait-Debugger
# Let's Create a Secure String :-D
$TestSecureString = "" | ConvertTo-SecureString -AsPlainText -Force

In a similar fashion, if you don’t capture the string, the debugger is able to continue, business as usual:

Wait-Debugger
# Let's Create a Secure String :-D
"Test" | ConvertTo-SecureString -AsPlainText -Force

The weird thing is that the code provided by @eamonoreilly and @ZanattaMichael is working just fine when debugged in vscode using the same powershell extension with “no configurations”