Visual Studio 17.7.0 Community Edition
Jump codes UI force closes when there is enough collapsed code above the jump location.
For example in a class like this one:
C#internal class JumpCodes
{
void Some27LineMethod() // 1
{ // 2
Console.WriteLine("3");
Console.WriteLine("4");
Console.WriteLine("5");
Console.WriteLine("6");
Console.WriteLine("7");
Console.WriteLine("8");
Console.WriteLine("9");
Console.WriteLine("10");
Console.WriteLine("11");
Console.WriteLine("12");
Console.WriteLine("13");
Console.WriteLine("14");
Console.WriteLine("15");
Console.WriteLine("16");
Console.WriteLine("17");
Console.WriteLine("18");
Console.WriteLine("19");
Console.WriteLine("20");
Console.WriteLine("21");
Console.WriteLine("22");
Console.WriteLine("23");
Console.WriteLine("24");
Console.WriteLine("25");
Console.WriteLine("26");
} // 27
public string JumpHere = "<---";
}
If no code is collapsed there is no issue. However if the Some27LineMethod is collapsed and visible on screen trying to jump to the JumpHere field closes the jump code UI. The UI closure takes place when entering first letter of the jump code navigating to the JumpHere field. The entered letter is typed normally as if the jump code UI was never activated.
Steps to reproduce:
- Paste the class
- Collapse Some27LineMethod method
- Keep both the collapsed method and JumpHere field on screen
- Open CodeRush jump codes UI (Caps + Tab)
- Enter the first letter of the jump code navigating to the JumpHere field (This is when the issue arises)
The issue doesn't seem to appear if the collapsed code is not visible on screen or if it's below the chosen jump location. Additionally jump codes seems to break only if the collapsed code preceding jump location has a certain minimal amount of lines. Collapsing any sort of content including comments, regions, methods and so on can break the jump codes when above jump location and long enough. Multiple shorter collapsed blocks visible on screen can also break jump codes (as long as they precede the chosen jump location).
Jakub,
Thank you for such a detailed bug report. I reproduced this behavior. We will investigate it and follow up once we have any results.