Build 4: Random Errors

Yesterday and today while working on a large web site project with
solution-wide analysis enabled, I noticed that ReSharper would suddenly flag
statements like <%=Resources.Blah%> out of the blue with "Ambiguous
invocation: void Write(bool) (in class TextWriter) void Write(char) (in
class TextWriter) ..." in aspx pages that hadn't been modified. The first
time it happened I was debugging a class when suddenly Errors in Solution
window popped up five or six aspx pages with errors. The odd thing is that
it would only flag one instance of <%=...%> with an error even the aspx page
might contain a dozen such instances. All I had to do was put a space after
<%= and then backspace and the error would go away. I haven't found any way
to reproduce it, though.

I've also noticed a few instances in which the Errors in Solution window
traps the keyboard and won't let me move focus anywhere. The last time it
happened, I could press Alt+W to drop down the Window menu but no other
keystroke would work in the menu. I was trying to Alt+W, 1 to set focus back
to the code editor window but it was as if the keyboard was dead with the
menu dropped down. I finally used the mouse to activate the code editor
window and everything was fine. I remember using AltShiftPgDn to go to the
next error and it set the focus to the Errors in Solution window instead of
going to the next error.

Finally, can the Errors in Solution be modified so the focus moves to the
code editor widow when pressing Enter on an error? If I double-click on an
error, it opens the appropriate code file and sets the focus to the line
with the error. If I press Enter, it opens the code file in the editor but
the focus remains in the Errors in Solution window. It's a minor thing, but
I try to keep my hands on the keyboard as much as possible.

3 comments
Comment actions Permalink

Hello Greg,

First of all, please check if this still happens for you with build 6 as
well? As to your last request, you're welcome to put a feature request through
http://youtrack.jetbrains.net/issues/RSRP. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Yesterday and today while working on a large web site project with
solution-wide analysis enabled, I noticed that ReSharper would
suddenly flag statements like <%=Resources.Blah%> out of the blue with
"Ambiguous invocation: void Write(bool) (in class TextWriter) void
Write(char) (in class TextWriter) ..." in aspx pages that hadn't been
modified. The first time it happened I was debugging a class when
suddenly Errors in Solution window popped up five or six aspx pages
with errors. The odd thing is that it would only flag one instance of
<%=...%> with an error even the aspx page might contain a dozen such
instances. All I had to do was put a space after <%= and then
backspace and the error would go away. I haven't found any way to
reproduce it, though.

I've also noticed a few instances in which the Errors in Solution
window traps the keyboard and won't let me move focus anywhere. The
last time it happened, I could press Alt+W to drop down the Window
menu but no other keystroke would work in the menu. I was trying to
Alt+W, 1 to set focus back to the code editor window but it was as if
the keyboard was dead with the menu dropped down. I finally used the
mouse to activate the code editor window and everything was fine. I
remember using AltShiftPgDn to go to the next error and it set the
focus to the Errors in Solution window instead of going to the next
error.

Finally, can the Errors in Solution be modified so the focus moves to
the code editor widow when pressing Enter on an error? If I
double-click on an error, it opens the appropriate code file and sets
the focus to the line with the error. If I press Enter, it opens the
code file in the editor but the focus remains in the Errors in
Solution window. It's a minor thing, but I try to keep my hands on the
keyboard as much as possible.



0
Comment actions Permalink

I think I found a clue today. I was working on the same website project and
updated a resx file and some aspx files from source control. Right after
this, ReSharper marked 19 files in error and all of the errors were in
<%=Resources.Blah%> statements in aspx files. Note that the files were
updated outside Visual Studio, so it makes me wonder if ReSharper loses
track of something when files are updated externally.

"Andrew Serebryansky"  wrote in message
news:c8a898dd1c6ef8ce740713d643e6@news.intellij.net...

Hello Greg,

First of all, please check if this still happens for you with build 6 as
well? As to your last request, you're welcome to put a feature request
through
http://youtrack.jetbrains.net/issues/RSRP. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Yesterday and today while working on a large web site project with
solution-wide analysis enabled, I noticed that ReSharper would
suddenly flag statements like <%=Resources.Blah%> out of the blue with
"Ambiguous invocation: void Write(bool) (in class TextWriter) void
Write(char) (in class TextWriter) ..." in aspx pages that hadn't been
modified. The first time it happened I was debugging a class when
suddenly Errors in Solution window popped up five or six aspx pages
with errors. The odd thing is that it would only flag one instance of
<%=...%> with an error even the aspx page might contain a dozen such
instances. All I had to do was put a space after <%= and then
backspace and the error would go away. I haven't found any way to
reproduce it, though.

>

I've also noticed a few instances in which the Errors in Solution
window traps the keyboard and won't let me move focus anywhere. The
last time it happened, I could press Alt+W to drop down the Window
menu but no other keystroke would work in the menu. I was trying to
Alt+W, 1 to set focus back to the code editor window but it was as if
the keyboard was dead with the menu dropped down. I finally used the
mouse to activate the code editor window and everything was fine. I
remember using AltShiftPgDn to go to the next error and it set the
focus to the Errors in Solution window instead of going to the next
error.

>

Finally, can the Errors in Solution be modified so the focus moves to
the code editor widow when pressing Enter on an error? If I
double-click on an error, it opens the appropriate code file and sets
the focus to the line with the error. If I press Enter, it opens the
code file in the editor but the focus remains in the Errors in
Solution window. It's a minor thing, but I try to keep my hands on the
keyboard as much as possible.

>

0
Comment actions Permalink

I think I found a clue today. I was working on the same website project and
updated a resx file and some aspx files from source control. Right after
this, ReSharper marked 19 files in error and all of the errors were in
<%=Resources.Blah%> statements in aspx files. Note that the files were
updated outside Visual Studio, so it makes me wonder if ReSharper loses
track of something when files are updated externally.

"Andrew Serebryansky"  wrote in message
news:c8a898dd1c6ef8ce740713d643e6@news.intellij.net...

Hello Greg,

First of all, please check if this still happens for you with build 6 as
well? As to your last request, you're welcome to put a feature request
through
http://youtrack.jetbrains.net/issues/RSRP. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Yesterday and today while working on a large web site project with
solution-wide analysis enabled, I noticed that ReSharper would
suddenly flag statements like <%=Resources.Blah%> out of the blue with
"Ambiguous invocation: void Write(bool) (in class TextWriter) void
Write(char) (in class TextWriter) ..." in aspx pages that hadn't been
modified. The first time it happened I was debugging a class when
suddenly Errors in Solution window popped up five or six aspx pages
with errors. The odd thing is that it would only flag one instance of
<%=...%> with an error even the aspx page might contain a dozen such
instances. All I had to do was put a space after <%= and then
backspace and the error would go away. I haven't found any way to
reproduce it, though.

>

I've also noticed a few instances in which the Errors in Solution
window traps the keyboard and won't let me move focus anywhere. The
last time it happened, I could press Alt+W to drop down the Window
menu but no other keystroke would work in the menu. I was trying to
Alt+W, 1 to set focus back to the code editor window but it was as if
the keyboard was dead with the menu dropped down. I finally used the
mouse to activate the code editor window and everything was fine. I
remember using AltShiftPgDn to go to the next error and it set the
focus to the Errors in Solution window instead of going to the next
error.

>

Finally, can the Errors in Solution be modified so the focus moves to
the code editor widow when pressing Enter on an error? If I
double-click on an error, it opens the appropriate code file and sets
the focus to the line with the error. If I press Enter, it opens the
code file in the editor but the focus remains in the Errors in
Solution window. It's a minor thing, but I try to keep my hands on the
keyboard as much as possible.

>

0

Please sign in to leave a comment.