I often get Code Analysis errors being highlighted in the editor window due
to not being able to resolve references, while the code compiles without
issue when using Build Solution or Rebuild Solution.

I am at a loss to explain this, I just know it doesn't go away by closing
and re-opening the file, only closing and re-opening the solution appears to
resolve it. I left it overnight to see whether it was just needed some time,
but no go, the code editor was still full of errors in resolving types,
which went away as soon as solution was re-opened.

The only non-standard thing I can think of, is that in our development
environment, common references reside on a mapped network drive S:.

Drive S: is mapped as follows:

• A network share named ProductName$ is created, with the appropriate
  

permissions for access by normal and admin users.

• A persistent mapping is then created for both the normal and admin users
  

(since VS2005 is run as admin on Windows Vista in our environment), to
\\MACHINENAME\ProductName$, for drive S:.

I have double and tripped checked that the network drive mapping is valid
(both VS and cmd.exe were started using "Run as Administrator", with the S:
drive mapping being accessible to both.

I have no idea whether this is causing ReSharper to think the assembly
references containing the types are no longer available, but just thought
I'd mention it as a possible contributing factor.

Issue was closed