We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From @rajivharris on April 20, 2018 2:12
VSCode Debugger Protocol now supports inline values for variables when debugging. It would be great if vsdbg/vsdbg-ui adds support for this.
Debugger Protocol: microsoft/vscode-debugadapter-node#78 https://github.com/Microsoft/vscode-debugadapter-node/blob/896566e0be3f48e5cf90fb715b3b3ffbfa777888/protocol/src/debugProtocol.ts#L1329-L1337
VSCode Support: microsoft/vscode#16129
Copied from original issue: dotnet/coreclr#17693
The text was updated successfully, but these errors were encountered:
From @RussKeldorph on April 20, 2018 16:29
@dotnet/dotnet-diag @tommcdon
Sorry, something went wrong.
From @noahfalk on April 21, 2018 0:37
@gregg-miskelly - I think this is for you guys more than it is for us? Let us know if there is a corresponding runtime part of the ask.
Here is documentation on the VS Code feature: https://code.visualstudio.com/updates/v1_9#_inline-variable-values-in-source-code
And some notes about how VS Code implemented it: microsoft/vscode#12256
I don't know how general purpose the VS Code implementation will prove to be. But we can give it a try...
Any news on inline variables for VSCode with OmniSharp?
No branches or pull requests
From @rajivharris on April 20, 2018 2:12
VSCode Debugger Protocol now supports inline values for variables when debugging. It would be great if vsdbg/vsdbg-ui adds support for this.
Debugger Protocol:
microsoft/vscode-debugadapter-node#78
https://github.com/Microsoft/vscode-debugadapter-node/blob/896566e0be3f48e5cf90fb715b3b3ffbfa777888/protocol/src/debugProtocol.ts#L1329-L1337
VSCode Support:
microsoft/vscode#16129
Copied from original issue: dotnet/coreclr#17693
The text was updated successfully, but these errors were encountered: