Skip to content

Conversation

@daviwil
Copy link
Contributor

@daviwil daviwil commented May 17, 2017

This change is part of the fix for PowerShell/vscode-powershell#619
which states that hitting a breakpoint in the integrated console does
not activate the debugger in VS Code. The fix is to check whether a
debugger client is connected when a breakpoint is hit, and if not, send
a notification through the language server to have the editor connect
its debugger client.

This change is part of the fix for PowerShell/vscode-powershell#619
which states that hitting a breakpoint in the integrated console does
not activate the debugger in VS Code.  The fix is to check whether a
debugger client is connected when a breakpoint is hit, and if not, send
a notification through the language server to have the editor connect
its debugger client.
@daviwil daviwil added this to the 1.1.0 milestone May 17, 2017
@daviwil daviwil merged commit 4f5e4ac into PowerShell:develop May 17, 2017
@daviwil daviwil deleted the console-breakpoints branch May 17, 2017 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants