I have several Business Object Libraries as well as other custom assemblies.  What is the best way to ensure that if one of these changes, a project that references it automatically gets updated with the current DLL?  I've been removing and re-adding these references (if they've changed) each time I compile a project.

Related to this question, I am referencing the Debug versions of these assemblies while I'm in development so that I can debug the DLLs as well as the project that references them.  Is there an easy way to make sure that when the project is built for release it points to the release versions of the DLLs?

Thanks!

There are a couple of ways of adding references. Usually, if you also control the source code, the easiest to just add the project to your solution. Right click on the solution, click add project, navigate to the project file and add it. This will not only allow you to debug it, but to work on it (if that is appropriate) right in the same solution. If you then look in your debug\bin folder of your startup project after you've built it at least once, you'll see all the referenced projects have been built and are sitting in this folder (they are also in there own debug\bin folders as well)...assuming your using the debug build. The one down side as near as I can tell is that the solution can take longer to build, because it will actually build all of the projects. If this won't/doesn't work in your situation, I'm sure there are others (definitely Trent and Ben) that can point you in the right direction as to the other ways of dealing with references.