I'm getting a wierd situation with VS.NET where (with about 6 VB.NET
projects in the solution - all either WinForms of class libraries) after the
first or second successful builds it will start throwing up compilation
errors saying things like a method is referenced that doesn't exist etc.

In all circumstances (related to the problem I'm describing) these errors
are not valid.  If VS.NET is closed and reoponed the solution builds
successfully the first time.

The errors it comes up with also tend to repeat, but not consistently.
Sometimes it'll be one, other times 20.  It's not clearly pointing to any
one class, although I am suspicious about inheritance, as when I work on a
base class the problem tends to occur quite rapidly.

Has anyone encountered this before???  Where should I start looking?  I've
un-installed and reinstalled VS.NET and it still happens.  It even happens
on a different machine.  This must be something funny in the project(s), but
as I said, they all successfully compile the first time.

Thanks everyone - I hope this is something simple, it's really beginning to
slow me down!

====
Phil