Skip to content

Conversation

@daviwil
Copy link
Contributor

@daviwil daviwil commented May 17, 2017

This change adds new behavior which causes VS Code's debugger UI to be
activated when a breakpoint is hit in the Integrated Console while not
currently in debug mode. This allows the user to set breakpoints and
run scripts from the console while still leveraging VS Code's rich
debugging UI.

Resolves #619.

This change adds new behavior which causes VS Code's debugger UI to be
activated when a breakpoint is hit in the Integrated Console while not
currently in debug mode.  This allows the user to set breakpoints and
run scripts from the console while still leveraging VS Code's rich
debugging UI.

Resolves PowerShell#619.
@daviwil daviwil added this to the 1.1.0 milestone May 17, 2017
@daviwil
Copy link
Contributor Author

daviwil commented May 17, 2017

Related to PowerShell/PowerShellEditorServices#455

@daviwil daviwil merged commit 0adcd2b into PowerShell:develop May 17, 2017
@daviwil daviwil deleted the console-breakpoints branch May 17, 2017 21:44
@rkeithhill
Copy link
Contributor

Surprisingly little code change on this side. Nice!

@daviwil
Copy link
Contributor Author

daviwil commented May 17, 2017

Yep! It was pretty easy to get working thankfully.

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.

3 participants