DLL administration

Question

I build some dlls to be used in a big application, and have a team working in the dlls heart of the application and another team working in the gui, but i am having a problems in the deployment of the dll's when a change is done, because the gui team needs or copy the new dll to the project folder, or delete the old reference and add the new one. Is there a best practice to deal with this problem?

I am using Visual Studio 2008 and devoloping int VB and C#

Thanks !!!

Answer 1

Put everything in source control (binaries if you must) and have people rebase when they need the new functionality.