Repository navigation
Improvements in breakpoint APIs for remote scenarios - #11312
Aditya Patwardhan (adityapatwardhan) merged 15 commits into
Conversation
|
The "hook in output" commit hooks up the ability to send output to the original client PowerShell without needing to invoke a pipeline on the server side. |
|
PoshChan-Bot (@PoshChan) please retry PowerShell-CI-static-analysis |
|
TylerLeonhardt, I do not understand the build target(s) |
|
PoshChan-Bot (@PoshChan) please retry static |
|
TylerLeonhardt, successfully started retry of |
|
PoshChan-Bot (@PoshChan) please retry static |
|
PoshChan-Bot (@PoshChan) please retry windows |
Paul Higinbotham (PaulHigin)
left a comment
There was a problem hiding this comment.
LGTM
|
Steve Lee (@SteveL-MSFT) - please update your review |
|
Steve Lee (@SteveL-MSFT) - please re-review |
|
🎉 Handy links: |
PR Summary
This addresses two things:
This is only added to the API surface for the PowerShell extension. In theory the breakpoint cmdlets can take advantage of this in the future.
PR Context
This will light up a scenario in the PowerShell Editor Services so that when you click to add a breakpoint, that breakpoint will be applied even if the PowerShell Integrated Console is busy running the
Debug-Runspace.PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.