Hey, Bonnie,

Thanks for your reply Yeah, I thought they might be two different issues.

I've noticed that if I get a legitimate compile error on a project/DLL that is the source of dependencies down the line, correcting the error and doing a full rebuild will generate all kinds of dependency errors. That's when I discovered that exiting VS.NET and reloading and rebuilding takes care of it.

Other thing I've noticed is that when I get bogus dependency errors, staying in VS.NET and recompiling each DLL one at a time will (sometimes) take care of it.

Like I said, it's never been a critical issue, but certainly one of the more annoying things about VS.NET. (That, and the fact that dropping a subclassed control onto a form winds up generating more code in the WinForms code generator than it should...really messes up inheritance).

I have learned not to rebuild in front of non-technical people. Once I made a simple change with some people watching me, and my next compile generated a ton of dependency errors. They watched me exit out of VS.NET and go back in...really had to dance my way around that one!

Kevin