342

When a compile fails in VB.NET in Visual Studio 2008, an Error List pops up at the bottom of the screen. To jump to an error, I double click on an error in the error list.

Is there a shortcut to automatically jump to the next error in the list? It gets a little bit tedious at times having to reach down and double click a list that I like to keep collapsed.

Brian Webster
  • 27,545
  • 47
  • 143
  • 218

3 Answers3

451

F8 (and Shift+F8 to go backwards).

Or at least that's what it is in my keyboard profile - you can go to tools\options\environment\keyboard and check out Edit.GoToNextLocation.

Note If you configured Visual Studio using VB keyboard settings, no key has been assigned to this function. You need to pick your own and assign them.

Carlos Muñoz
  • 15,816
  • 7
  • 50
  • 76
Brian
  • 113,581
  • 16
  • 227
  • 296
  • 6
    If you configured Visual Studio using VB keyboard settings, no key has been assigned to this function. You need to pick your own and assign them. – Bill Nov 09 '09 at 13:01
  • Works with C++ projects, too. – ahans Apr 18 '13 at 14:18
  • 13
    If luckily you don't have errors F8 goes to next warning. – Tomasito Mar 05 '14 at 13:16
  • 2
    so messed up. was happy to find that it was assigned to F4 in my config. but F4 is set to swit chthe current display on my laptop. so much to deal with... thanks though. solution (CTRL+SHIFT+F12) below worked. – victor n. Sep 30 '17 at 01:22
  • 3
    Important: at least for VS 2017, I needed to in my "error view" have selected both "Build + Intellisense" in order for these shortcuts to work. – Johan S Feb 22 '18 at 10:23
  • 1
    You can restrict this to errors in the current document or project using the drop-down in the Error List (defaults to whole solution). – Warlike Chimpanzee Aug 05 '18 at 19:11
  • 3
    Just in case if it wasnt clear, `F8` jumps to next item (be it errors, search results, symbol reference search etc). It depends on which pane had your focus last. – nawfal Feb 07 '20 at 10:05
179

Funny because I use CTRL+SHIFT+F12 which is View.NextError.

I wonder what's the difference between View.NextError and Edit.GoToNextLocation.

Matthias Braun
  • 24,493
  • 16
  • 114
  • 144
Luis Filipe
  • 7,762
  • 6
  • 42
  • 72
  • 15
    Edit.GoToNextLocation works also when you navigate through search in files results – GôTô Aug 24 '12 at 10:46
  • 9
    When dealing with multiple projects I find `View.NextError` much more useful. This way I don't navigate to errors in other projects. – Joel Aug 06 '13 at 12:19
  • 3
    One diff between View.NextError and Edit.GoToNextLocation is that View.NextError is specific to the error list, but Edit.GoToNextLocation is applicable to error list, search results, find all refs etc – anish Jul 18 '17 at 14:25
  • definitely more useful. and beside F8 above is just decreasing my screen brightness. – victor n. Sep 30 '17 at 01:17
  • 3
    @victorn.you might have `Fn` keys active. Try to press `Fn`+`F8` – Luis Filipe Oct 02 '17 at 07:47
  • Works in VS2019. – JWP Mar 30 '20 at 21:29
21

If you have ReSharper installed, you can use ReSharper.ReSharper_GotoNextErrorInSolution, the default mapping for which is Shift+Alt+PgDn. This is the equivalent of clicking on the error icon shown in the bottom right of Visual Studio's status bar:

ReSharper solution errors screenshot

Simon MᶜKenzie
  • 7,576
  • 13
  • 43
  • 67
  • 4
    Useful; thanks. Seems that `Alt`+`PgDn` does the same thing, but for Warnings. – CJBS Apr 13 '17 at 17:42
  • Better than the default VS shortcut which seem to also always include warnings, so here you can pick if you want to include warnings or not which is nice. – jeromej May 26 '20 at 13:16