dotnet/roslyn

Visual Studio not correctly highlight selected ITEMS in subWindows rows

Open

#39,826 opened on Nov 14, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-InteractiveBugDeveloper CommunityInteractive-Debugginghelp wanted

Description

This issue has been moved from a ticket on Developer Community.

1. I set brakepoint (see above) and press F5.2. Then, in subWindow "local Variables", I select "array[0]" and "array[1]" (and that subWindow "local variables" highlight right rows).3. Then I press "F10"...BUT!!! subWindow "local variables" highlight other two rows: "array" and "array[0]"!!!!!But I Want to see highlighted that rows in subWindow, that I selected!!! == problem!!!!Summary: subWindows highlight rows by top-order, but need highlight user selected rows!!! Image:104544-1st-step-before-sortcomparison-line.png Image:104545-2nd-step-after-sortcomparison-line.png

Original Comments

Visual Studio Feedback System on 11/13/2019, 11:22 PM:

Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We'll provide an update once the issue has been triaged by the product team.

Contributor guide

Tech stack
csharp
Domain
developer experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Visual Studio debugging basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The issue describes a problem with the debugger's locals window highlighting after stepping. To investigate, one should examine the Visual Studio debugger's internals, specifically how the locals window updates its selection during debugging. The original developer community post contains images that may clarify the expected behavior. Since this is a Visual Studio issue, it might be more appropriate to file in the Visual Studio repository rather than Roslyn.