I loaded up an old solution in ReSharper 5.x, and noticed that this line of
code is flagged. It's an old ("C") coding style, written by a developer
that left long ago... but the code does work and is fine, and should not be
string directories = Directory.GetDirectories(path);
for (int i=0, ic=directories.Length;i<ic;i++)
if (directories[i] != path)
The code "ic=directories.Length" is wavy-underlined with the tool tip saying
that the 'for' loop variable is never modified.
Clicking on it brings up a quick-fix icon with the only option being to
suppress the inspection.
But the control variable is "i", not "ic"... "i" IS modified, and "ic"
should NOT be modified. So the code, archaic in style as it is, is correct.
I don't know exactly how smart ReSharper can be about this, but perhaps it
could be a little smarter than this. Or is there really an issue here that
I'm missing (I'm always hesitant to question ReSharper, because it's so
often correct :)