Does anyone know if there is a whitepaper/FAQ/Blog/best practices, etc. about maintaining projects, solutions, a references in them for VS.NET?

I'm finding myself in the situation where I've got a couple of projects being used between multiple projects (as references) & solutions.

(just for some background)

For example, I have an ErrorLog project that handles error logging. I've got classes from MM.NET, and classes from the west Wind Web Store all shared between a few different projects.

One project is a set of business objects.
Another project builds XML and uses the WWStore class to communicate with a third party.

These various projects are being used in different apps. For example, one app. is a webservice which exposes some functionality of the business objects and the XML project. Another one is a windows service that also uses the XML project and the WWStore class libraries. Another one is a desktop app. that lets me test the XML generation process and view a log of web service activity and activity happening in the windows service.

At any rate, the issue I'm starting to have is when I make changes to some of these "core" libraries. Suddenly my other projects start complaining that they can't copy the DLL over because this version will conflict with another version built into another project. I have to open up all these other projects, remove the reference, add it back in, and recompile them. I guess I could put these in the GAC, but I'd like to keep deployment simple (and I'm not sure that I'm not going to end up having to update everything anyway to make sure I'm using the same versions of everything everywhere). Debugging this is even worse, since it won't load the symbol library for things since they're out of sync with the DLL.

Another issue is referencing other DLL's when I'm still in the test process. The DLL's get built into the bin/Debug directories. So if I want to use them I have to reference this directory instead. What happens when I go to release this and they get dropped into the Release directory?

So far, I've been doing a lot of this stuff manually, but it really feels like I'm fighting the dev. environment each step of the way. I guess I can also start modifying the default settings to place things in a common directory, etc., but before I do this I want to get an idea of how I'm "supposed" to be doing all of this.

Everything I've been able to find doing Google searches is pretty useless (and not on topic).