Anyone having problem with F8 (next error) key with 4.1?

I've noticed a problem with my F8/Shift-F8 keys since using 4.1 (never used 4.0, uninstalled 3 long ago due to performance problems, but never noticed this behavior with 3 as far as I recall). Resharper is the only add-in I have installed so seems like it is related to that.

Specifically, if the error window has focus, pressing F8 goes to the next error as expected. But now pressing F8 again does nothing, unless I set focus again to the error window. So F8 (and Shift-F8) with focus in the editor is not working for me. Anyone else have this happen (and know a solution?).

Usually if I unload VS (2008 btw) and restart it, it seems to start working again normally.

Edited by: Scott Clarke on Oct 4, 2008 9:18 PM

2 comments

Hello,

I've noticed a problem with my F8/Shift-F8 keys since using 4.1 (never
used 4.0, uninstalled 3 long ago due to performance problems, but
never noticed this behavior with 3 as far as I recall). Resharper is
the only add-in I have installed so seems like it is related to that.


We're not using the error list that much (no wonder, as R# highlights most
errors before we compile). But F8 is OK when I'm working on C++/CLI projects
with R# on.

Specifically, if the error window has focus, pressing F8 goes to the
next error as expected. But now pressing F8 again does nothing, unless
I set focus again to the error window. So F8 (and Shift-F8) with focus
in the editor is not working for me. Anyone else have this happen (and
know a solution?).


Is the F8 key suppressed only if you go to a C# editor?

PS just checked on XAML and C#: after compilation, I clicked the first error
in the Output window, then F8ed to all the rest without a problem.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Well it's kind of random for it to start doing it, and as I said it usually will work correctly again if I unload VS and restart. This week it has only done it once. When I was googling it, I did notice an (unresolved) issue for the same thing (or sounded the same) for version 3.

I only use c# so that's all I can comment on, haven't noticed whether it does it in xaml since I never use the error list with that.

Anyhow, not a major issue for me at this point since it'll work right most of the time.

0

Please sign in to leave a comment.