All geek questions in one place

TFS 2012 automatically creates projects that depend on the current

Okay, so I have to admit that I'm very new to all of these build automation tools. But basically what I am interested in is a way to relate my assembly definitions in such a way that if I have such a case

  • ProjectA creates ComponentA.dll
  • ProjectB refers to ComponentA.dll and produces ComponentB.dll
  • Links ProjectC ComponentB.dll

then when I make changes to ProjectA and check them out, the build process will automatically create ProjectB and finally ProjectC, and report any errors.

So, is there a way to do this, or if this type of thing will be handled somehow completely differently in the first place?

+2
source share
2 answers

The process you are talking about is the essence of the practice known as Continuous Integration .

TFS does this very well: just set the Trigger assembly definition to Continuous Integration and set Workspace to the parent folder of the three projects. Thus, any change in one of the projects will cause assembly.

MSDN: constantly create and deploy

+5
source

You can use the visual studio solution and use links to projects between projects. Then create the solution on your build server.

0
source

Source: https://habr.com/ru/post/1483608/

More articles:


All Articles