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!

Ah, well, I thought I'd chime in just in case.



Also, I do know that the project file for a project is actually just a MSBuild file. MSBuild is used every time you compile the project/solution. I also know that you can switch between debug and release builds within VS, but I have to hunt around for it every time. I'm pretty sure you can use multiple solution files to create special case builds. It confused the heck out of me the first time I looked at the SF source...what the heck were all those solution files!?! They explained all that in the class



If you happen to run across a GUI tool that would build/manage MSBuild files, let me know. Good luck!

If the version # of your referenced DLLs changes, you will have to remove and re-add them just like you've been doing (say from 2.1.0.503 to 2.1.0.510 or something).  However, if the version number does not change, but you have an updated DLL, just close and re-open Visual Studio after you have moved the new DLL to the place where your project references it and you'll be fine, no need to remove and re-add it.