Current Statement Highlight Bug (ver 4.0)

Recently installed ver 4.0 (fresh install) on XP SP2 VS 2005 and functionality in Visual Studio where, as you step-through code in Debug mode, the current statement which the debugger is on gets highlighted...
(even when it's a piece of the current line - as in a line like "foreach (object o in collection)")
This functionality is broken... The current statment does nto highlight as it should, although the thin vertical bar indicating the current insert position moves around appropriately... Also, I notice that when the current Statement is a class name, as in a line like:
foreach(MyClassName refVar in MyClassNameColelction)
where Vsual Studio would normally highlight the word "MyClassName", (as the code steps through the internal enumerator), with Resharper installed, I notice that the foreground color of the word DOES Change from the cyan color (cause it's a defined class) to Black, (which is the default foreground color for Current Statement Highlight in Visual Studio Menu, "Tools | Fonts and colors | Current Statement"

As a test, I changed the foreground color there to see if that would affect at least the foreground text color, but it has no effect either.

If I uninstall Resharper, it comes back...
If I disable Resharper using tools, Addin Manager, the behavior is unaffected, (it is still broken)

I tried this on two different XP machines with same result.

Everything works fine on my Vista machine...

Any one else have this issue? If so, has anyone fixed it?

Edited by: charles bretana on Aug 22, 2008 1:58 AM

9 comments

Hello,

There was at least one more case reported, also on WinXP.

As you said, the behavior can be reproduced even when R# is not running.
This means that R# behavior is not in effect, but rather some static change
to the Visual Studio environment settings. Thus, it might be the number of
highlighters available when R# is installed, or something like that. We'll
try to collect more info on that.


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


0

Yes, thank you !

To be clear, when I un-install Resharper, completely, the highlighting reappears, and it works normally again, (and re-installing R# re-breaks it)
Whereas when I simply disable R# using add-in manager, the problem remains...

To me, that might indicate that the issue is related to some part of R#, (or some aspect of Visual Studio settings/functionality) which is modified by R# installation, and NOT reversed by disabling it in VS Add-In Manager) but which IS reversed by unInstalling R#...

Please let me know if you discover any other avenues worth investigating...

If it matters, both of the boxes I have found this on have had Visual Studio 2008 installed as well (although it has been uninstalled on one without correcting this issue,)

0

Hello,

To be clear, when I un-install Resharper, completely, the highlighting
reappears, and it works normally again, (and re-installing R#
re-breaks it) Whereas when I simply disable R# using add-in manager,
the problem remains...


Yes, that's what I meant — when the active part of R# is disabled (but the
passive installation is still present), the problem would still reproduce.

If it matters, both of the boxes I have found this on have had Visual
Studio 2008 installed as well (although it has been uninstalled on one
without correcting this issue,)


To be sure — you do have VS2005 SP1 installed, right?

I could not reproduce this behavior in our test environment. However, if
SP1 is missing from VS2005, this behavior is by design (of Visual Studio).


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


0

Serge,

I'm not at the office at the moment where the XP machine is at,
but on my home Vista machine, (see attch image jpeg) it says I have

Microsoft Visual Studio 2005
Version 8.0.50727.867 (vsvista.050727-8600)
(no mention of SP1)

and

Microsoft .NET Framework
Version 2.0.50727 SP1

This machine, of course, does not exhibit the issue (It's Vista - not XP)
I attached an screen shot of this machine, (with Vista) where the highlight IS working...

When I get to the office tomorrow, I willl check to verify that it has SP1 on it,
but should I be looking at SP1 for Visual Studio, or SP1 for the .NET Framework ?

If Visual Studio SP 1 is not installed, I will get it added, and then check the behavior and get back to you.

Not important, but I have a question about yr last post. What do you mean by "by design (of Visual Studio)" ?
You can't mean that Visual Studio's out of the box design is to not highlight the current statement after R# has been installed, Are you talking about some other design behavior in VS2005 (pre-SP1) that inadvertently conflicts with R# ?

0

Hello,

When I get to the office tomorrow, I willl check to verify that it has
SP1 on it, but should I be looking at SP1 for Visual Studio, or SP1
for the .NET Framework ?


Visual Studio 2005 Service Pack 1.

Not important, but I have a question about yr last post. What do you
mean by "by design (of Visual Studio)" ? You can't mean that Visual
Studio's out of the box design is to not highlight the current
statement after R# has been installed, Are you talking about some
other design behavior in VS2005 (pre-SP1) that inadvertently conflicts
with R# ?


In a clean VS2005, there's a limit on the number of registered text markers.
Visual Studio own markers plus R# markers exceed this limit. There is no
explicit error, no indication of a failure, no silent failure either — but
the colors start mixing up. For instance, you could see a class highlighted
in red even though the Fonts'n'Colors settings are for green. We were shipping
a Microsoft hotfix until the Service Pack released.


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


0

Bingo! That sounds like the nail on the head! I have also experienced colors getting mixed up, like I am seeing color scheme assigned for Breakpoints (with dark maroon background) applied to Unused variables, and other such anomolies. And thsi would also explain why the issue is not easily reproducable, as other things may affect how quickly the limit on theswe things is exceeded, no? I'll bet SP1 is not on my machine at work... But I will let you know first thing in the AM (Czech time)

Thanks,

0

My Visual Studio at work is indeed the RTM version (8.0.50727.42). I am having IT support install SP1 today. Although I fully expect that will fix this. After I get SP1 installed, I will post here and let you know for sure so you can close this issue.

0

Hello,

My Visual Studio at work is indeed the RTM version (8.0.50727.42). I
am having IT support install SP1 today. Although I fully expect that
will fix this. After I get SP1 installed, I will post here and let you
know for sure so you can close this issue.


Thank you for the information.

I was sure this SP is silently installed by Windows Update, so I didn't consider
it to be an any probable reason for the highlightings problem. It's possible
that this applies to Vista only, though.


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


0

No, unfortunately,
In my case, the client is a government agency with onerous restrictions on what can / cannot be installed by users... This update has to be installed manually by a help desk technician! (don't ask why)

0

Please sign in to leave a comment.