Bonnie,

OK, sorry for the confusion, I guess I misspoke.

In some instances, recompiling one project takes care of the situation, but in others I have to recompile, exit VS, and then go back in.

Anytime I need to make a change to a project that also exists as a reference/dependency for something else, I now rebuild manually one at a time, in the same order that I previously defined in my solution build order. That way, the impact of 'compiler confusion' is minimized.

Yes, I checked the Config Manager ;) (actually, I wasn't fully aware of it until a few months ago when you responded to another post).

I'm using some third-party DLLs from devcomponents now that I wasn't using when I was working with VS2002. I use a few as part of a base class container. So that might explain my perception that VS2003 has more issues than 2002.

Admittedly, I scrapped my solution and started building 'manually' out of frustration. Maybe I need to let some time go by and try it again when my head is 'fresher' ;)

Kevin