For the last period I actually wrote some new infrastructures and upgrade some other older infrastructures.
Those infrastructures live in separate solution, and we are using it from our different projects, this infrastructure-solution output (DLLs) are also in use by other programmers from other teams.

In our project-solution we use file reference to those DLLs, using the copy local option, which should cause a copy of the DLLs to the bin directory in the project-solution.
This kind of copy should occur every time we build the project and the DLL in the bin directory deferred from the DLL we referenced to (origin path of the DLL).

Most of the time I am working on at least 2 different solution (1 for infrastructures and 1 for my project) and I found out that sometimes after compile my infrastructure-solution and then compile the project-solution the Copy-Local = true does not really copy the file.
The result is that you are thinking that you are working on version x.y.z.12 but you are actually working on version x.y.z.11. Believe me it could be very frustrating.

Steps to cause the copy-local to work:
1) Delete the DLLs from the bin directory (project-solution).
2) Build the (project-solution).

I've searched some further details an found this Jelle Druyts's post talking about the same behavior and found the same solution (=none).

Finally, I have my own mediocre solution, while working in solution with file reference that are enable that copy local, add the solution pre-build script for deleting all the files from the bin directory.
Any other answer (at least those I've heard) to this problem would be build-time-consumers.

At my Team we work on different applications simultaneously, each application live in a separate solution.
The common denominator between those different solutions is one solution which hold some WebControls, scripts (for the web controls) and some other methods which serve the BL and Dal.

I am gonna talk about the WebControls and their scripts.
As you can understand, each application (solution) holds a reference to the WebControls DLL, but What are we going to do with the scripts? 
I prefer to write a pre-build event script which will deploy (simple XCopy) the scripts to the Inetpub and than each application could use those controls without copy the scripts to their private directory hierarchy.

Yesterday we start using another Solution, IEWebControls (which most of you probably know their controls such as tabstrip, treeview etc.), while installing the IEWebControls it will create a directory on your computer and after running their build script it will copy the scripts into the Inetpub.

We made a discussion about how we should use the the DLL and the scripts so all the programmers could make a simple get from the VSS, and every one could use those WebControls, there are two different opinions:
1) each programmer should make his get (only for the scripts) from the source-safe into the Inetpub directory (the references to the DLL is already exist in the relevant solutions).
2) each programmer should get the full solution and make a build, the build will cause the XCopy for the relevant scripts to the exact directory.

I prefer the second, because it will be exactly like our WebControls solution which I describe earlier,
also it will be similar to regular deploy to our the servers, finally I think that this is the right logic for all changes (if exist - DLL/scripts) to take place at one click (build).

I would like to hear your suggestions, What do you think about my preferred way.