" you must be one of those people who reformat their hard drives on a regular basis. <g>

Yup, once a week, whether it needs it or not! ;)

Sorry, I don't mean to be difficult, I've just had a general frustration with the .NET IDE. Until .NET came along, my main experiences with an IDE and project builder were VFP and the old Borland compilers, and I really feel that those were more solid by comparison.

I'll retract what I said, because I just pulled up an e-mail from two years ago on VS2002 (not only do I reformat drives every week, I also save old e-mails!), and I recall more clearly all the problems in VS2002. There were many instances where legitimately fixing a syntax error resulted in a slew of bogus compiler syntax errors. So I'd sit there for 10 minutes, staring at code that was actually fine.

In the last half hour, I rebuilt my framework and development solution from scratch, based on the diagram I've maintained in Visio. It built fine. I then introduced a syntax error in a low-level class, did a build, then fixed the error and did a build again and then a rebuild all, and it basically worked the way I expected.

It's possible that somewhere along the line, I screwed up a dependency or had a missing or invalid reference. I think in general, anytime I make a change, if I do a single build on that DLL, and only do a rebuild all when I get a clean single build first, maybe some of problems I've had will decrease.

Sorry to be the problem child...
Kevin