Calling Set-PSBreakpoint in console doesn't cause breakpoint icon to appear in file
See original GitHub issueWe 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 (https://github.com/Microsoft/vscode/issues/24164) which causes all other breakpoints in the file to be cleared when the BreakpointEvent is received.
Issue Analytics
- State:
- Created 6 years ago
- Comments:14
Top Results From Across the Web
Troubleshoot Breakpoints in the Visual Studio Debugger
To modify a single breakpoint, hover over the breakpoint icon in the editor and select the settings (gear) icon. A peek window is...
Read more >Pause your code with breakpoints - Chrome Developers
Use breakpoints to pause your JavaScript code. This guide explains each type of breakpoint that's available in DevTools, as well as when to ......
Read more >How do I remedy "The breakpoint will not currently be hit. No ...
Right-click it and select Symbol Load Information. You'll get a dialog that lists all the directories where it looked for the .pdb file...
Read more >Debugging in Visual Studio Code
An inline breakpoint can be set using Shift+F9 or through the context menu during a debug session. Inline breakpoints are shown inline in...
Read more >Debugging in the browser - The Modern JavaScript Tutorial
The “Sources” panel · Console · Breakpoints · The command “debugger” · Pause and look around · Tracing the execution · Logging ·...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yep, I think this could work in enough scenarios to satisfy the need in the short term, and on older PowerShell versions.
Roman, feel free to send an e-mail anytime with questions about how to get this hooked up. I’m looking for the docs on the high level details right now, I’ll pass them along to you soon.
I’ve been waiting on @PaulHigin to add the ability to break on unhandled terminating error and it hasn’t happened yet AFAIK. This could be interesting way point until we get the built-in support in the debugger.