Clearing "object browser" cache in VS.NET

[Mike Scott]

I'm having strange problems with VS.NET. When trying to go to definition,
sometimes I get dropped into the object browser with the top assembly
highlighted, rather than going to the definition in my source code. The
source is part of the project, or is in an assembly that's part of the
solution and referenced as a project assembly.

The weird thing is that I can go to definition on most classes, methods,
etc. but a few don't work.

Is there an object browser cache that I can clear, or can I tell VS.NET to
rebuild its object browsing cache?

Cheers,

MikeS.

 

[Cowboy \(Gregory A. Beamer\)]

1. Is this in a separate project in your solution?
2. Do you have a .NET reference or a project reference?

If your reference is on the compiled version (ie, a .NET reference), whether
it exists in your solution or not, it will assume it is compiled and go to
the object browser. Not sure if this helps.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****