Sharing shared libraries in a large team and tracking used libraries

Question

I belong to the .NET store using TFS. Last year or so, we tried to share between our teams (some local, some in a completely different region).

So far, we have included common code as a reference to the project. As the dependence on common code grows, we have more and more problems (people change code that violates other applications, updates the project to the new version of Visual Studio, etc.). As a result, I tend to make people refer to code as compiled binaries (dlls). The code itself will be maintained and updated regularly by the designated team. The source code will be read-only so that people can make changes / corrections and send it to the team for verification and redistribution. What do you think of this plan? Is there a better way?

I feel that the disadvantage of this plan is that I trade one set of headaches for another. If I have many different versions of the library, how can I know for sure which versions are used and which are not? Is there any way to do this through TFS? I believe that if we know exactly which versions are used, we can know the extent to which we should worry about backward compatibility, with whom we can contact if we have problems, etc.

How do some of you work on large teams?

Answer 1

refers to code as compiled binaries (dll)

. , , . / . , .

,

: ? , , , . , , , / , - . , , , HTTPS. . , script , TFS, .

Answer 2

,

:

• . .

• , /. - .

• . , . , .

• . , , .

Answer 3

We distribute assemblies in different teams. If a method or overload needs to be changed in a specific version, we save the old method as [Obsolete("message")], add a new method, and then in future versions we delete the obsolete method. Thus, developers have enough time to use newer versions.