Skip to content

A few improvements to the interactive debugging experience #401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 22, 2017

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented Mar 22, 2017

No description provided.

daviwil added 2 commits March 21, 2017 17:40
This change causes a message to be displayed in VS Code's Debug Console if
the user tries to execute a command there while debugging a PowerShell
script.  The message directs the user to open the Integrated Console
instead.

Resolves PowerShell/vscode-powershell#596.
This change causes scripts executed in the debugger to be dot-sourced into
the shared session so that the functions defined in the script can be
experimented with after debugging is complete.

Resolves PowerShell/vscode-powershell#540.
@daviwil daviwil added this to the 0.11.0 milestone Mar 22, 2017
daviwil added 2 commits March 22, 2017 15:44
This change enables debugger commands in the integrated console by acting
on the DebuggerResumeAction that is returned by the debugger when a
command gets executed.  If a DebuggerResumeAction is returned, it is used
to resume the debugger in whatever way the user requested by typing a
command.

Resolves PowerShell/vscode-powershell#600.
@daviwil daviwil merged commit 6213d1b into PowerShell:develop Mar 22, 2017
@daviwil daviwil deleted the debugger-polish branch March 22, 2017 22:49
@rkeithhill
Copy link
Contributor

Nice enhancements!

@daviwil
Copy link
Contributor Author

daviwil commented Mar 22, 2017

Yep, this will be a nice little mini-release :)

TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
…unsupported

This change adds some extra logic to Start-EditorServices.ps1 and the
SessionManager class to properly report to the user if their PowerShell
version is unsupported (PowerShell v2 or below).
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
Fix PowerShell#401: Session startup should indicate if PS version is unsupported
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
…error

This change improves a previous fix where we report an unsupported
PowerShell version when the user attempts to start the extension.  The
previous fix utilized ConvertTo-Json to write out the session details;
this caused a failure since this cmdlet was introduced in PowerShell v3.
We now write out teh JSON manually in this case.
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
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