Shortcut to go to the next item no longer works in the Find Results window

I'm using Visual Studio 2022, version 17.14.34.

For years, I've used the F4 shortcut (mapped to "Edit.GoToNextLocation") to move through the items in the ReSharper "Find Results" window. It's very convenient, and I use it all the time (and I also use Shift+F4, of course).

A few months ago, I installed ReSharper 2026.2, and since then the shortcut no longer works. I haven't found any other shortcut to move through the items in the results window.

Fortunately, going back to ReSharper 2026.1.1 restores the functionality.

At the time, I assumed it was a bug in the first 2026.2 release and that a later update would fix it, since the bug was so obvious. So today I installed ReSharper C++ 2026.2.3.1. To my surprise, the bug is still there, and I don't understand why it hasn't been noticed and fixed yet.

I hope you can fix this soon.

Please note that F4 works with the rest of Visual Studio, for example, to move from one compilation error to the next. Consequently, this is undoubtedly a problem with ReSharper 2026.2.x

0
4 comments

Hello,

This seems like an issue with the out-of-process mode (RSRP-501686). Please switch to the in-process mode as a workaround.

Thanks!

0

Thank you very much; it indeed works. I wonder why ReSharper switched to out-of-process mode without asking for my opinion. I never really understood the purpose of this mode, since for me, the in-process mode works very well despite a very large project. 

0

Another alternative is R#'s own shortcuts for next/previous location bound to Ctrl-Alt-PgUp/PgDn by default.

0

Hi,

Out-of-process mode was developed to perform intensive analysis tasks outside the Visual Studio process, prevent the user interface from freezing, maintain smooth typing, and address numerous performance issues.

Starting with version 2026.2, this mode is enabled by default. 

You may switch back to In-Process mode if you encounter any issues while using OOP mode. Please do not hesitate to report any issues you experience in OOP mode so that we can address them. 

 

0

Please sign in to leave a comment.