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.