Can TFS projects link to each other?

Question

I recently started working in a corporate software environment where hundreds of different applications were limited to their own silos. One of my tasks is to try to standardize things a bit, and the first attempt will be standard event logging. The standard company is currently "everyone should use the corporate library for journaling." In fact, this means that different developers working on different projects implement different logging in different ways, and just use this library most of the time.

To this end, I want to ignore the actual logging tool behind the built-in company standard interface. The idea is to focus on the fact that the “standard” is far from the implementation tool and how it is used. Applications will then use the internal library and do not belong to the tool behind the scenes (with the possible exception of the app.config section, although I already know how to abstract from it using log4net).

However, the problem I am currently facing is that all of these applications are in separate TFS projects. If I create a project that contains a common logging library, is there a way for other projects to reference it? I do not want to distribute the library among each project, because they will quickly go out of sync.

If TFS cannot do this, does anyone have any other suggestions?

Answer 1

TFS "" (, Visual SourceSafe). , , "" . , :

• , . Logging, A) , ( "push" ) B), , , ( "pull" ).

• . , , - -, , ( / ).

( , ), , .

, .

Answer 2

, . API- - , . . CI, Beta Release . / , . TFS , , . Pull , . , , .

, .

Answer 3

TFS , , . , . , , . , . , , , .

Answer 4

TFS 2018:

(.csproj), TFS 2018, DLL, 2 :

1. . . . ( .csproj, )

    <ProjectReference Include="..\..\..\OtherTFSProject\src\ProjectDLL\ProjectDLL.csproj">
      <Project>{e8ed9a74-a9e9-47de-ab08-0b554a950606}</Project>
      <Name>ProjectDLL</Name>
    </ProjectReference>

2. TFS2018, , " " TFS. , .

- . , !

Answer 5

Just deploy all the major libraries in the GAC so that applications can receive the latest data from the GAC with every update. You can easily push the GAC to all “servers / workstations” with the command. Remember to save the signature of all Public methods in your DLL constants, otherwise developers will get an error when changing the library (if they refer to this method)