Calling Set-PSBreakpoint in console doesn't cause breakpoint icon to appear in file

[daviwil]

We need to send a BreakpointEvent back to the debugger client when new breakpoints are added in the session via the Set-PSBreakpoint cmdlet. I've got an implementation working but it's currently blocked by a bug in VS Code (microsoft/vscode#24164) which causes all other breakpoints in the file to be cleared when the BreakpointEvent is received.

[daviwil]

Here's the commit with the current work: daviwil/PowerShellEditorServices@5beeba1

[nightroman]

And the opposite is true, in a way. Namely,

• set a breakpoint by F9 is a script
• in the terminal invoke Get-PSBreakpoint

As a result, the BP is not in the output.
Also, if I invoke this script from the terminal then the BP is not hit.

Is it the related issue or should I open another?

[daviwil]

I don't think there's an issue for it specifically right now, but this is actually a problem with VS Code's debugger model. When you click a breakpoint in a file when the debugger isn't running, they don't send me any notification that the breakpoint was created. They wait until the user starts the debugger before sending the breakpoints to my debug server. I'm trying to get them to expand their model to support scenarios like this but it's a slow process.

[nightroman]

I am looking forward to this development. It's probably too early to file all hiccups in debugging.

I am playing with some useful scenarios in VS Code debugger, e.g. automatically breaking into the debugger and opening scripts on terminating errors at the point of failure. It's promising but not quite reliable yet.

[daviwil]

Definitely not too early! File everything that you run across that doesn't work well for you, I'm hoping to polish out most of the issues over the next couple of months.

[nightroman]

All right, I will create some issues then after a while when I get more facts.

[daviwil]

Thanks Roman!