Open vsfeedback opened 3 years ago
Tagging subscribers to this area: @tommcdon See info in area-owners.md if you want to be subscribed.
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
--- ### Original Solutions (no solutions)Author: | vsfeedback |
---|---|
Assignees: | - |
Labels: | `area-Diagnostics-coreclr`, `untriaged` |
Milestone: | - |
@lewing I'm not sure whether this is even supported?
Tagging subscribers to this area: @thaystg See info in area-owners.md if you want to be subscribed.
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
--- ### Original Solutions (no solutions)Author: | vsfeedback |
---|---|
Assignees: | - |
Labels: | `arch-wasm`, `area-Debugger-mono`, `area-Diagnostics-coreclr` |
Milestone: | Future |
This is a known limitation of the current debugger. We hope to address it but the work isn't currently scheduled.
This issue has been moved from a ticket on Developer Community.
[severity:I'm unable to use this version] The debugger is paused over a breakpoint. It allows me to inspect the value of the local variables but not edit them. The edit value is ignored and replaced with the original value. Sometimes I see an Invalid Expression error pop up box...
Original Comments
Feedback Bot on 11/23/2020, 06:53 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Original Solutions
(no solutions)