All geek questions in one place

Dependency Management / Team Projects in Team Foundation Server 2010

I am trying to find the best way to logically separate projects in TFS 2010. Currently we have three separate projects:

  • The main wireframe project that runs on the server
  • A console application that references the underlying DLL structure.
  • A web application that also refers to a basic dll structure.

TFS splits projects into Team Projects. All three of these are truly separate “projects,” but the last two are dependent on the .dll help system. In the Java world, you can set up dependency management, where the base structure will be created and published in the central repository in the company, and client projects can be checked separately and just refer to the dll in the repository so that no project crashes.

Does TFS support dependencies? Should these three projects be created in separate team projects or in the same? Can you build projects as a team?

What is the best way to create team projects, so there are minimal problems with dependencies, but they are also partitioned so that they can be individually processed, and embedded scripts can access all projects for CI?

+3
source share
3 answers

TFS Team projects are not comparable to what you understand as a software project / solution. Basically, a team project is a container for a bunch of things that you want to keep together.

, , . , , . CI, , , .

.

+4

TFS , , , , : File- > Source Control- > Source Control...

, , .

, .

, , .

+2

Why do you even need dependency management in TFS?

You need your general assembly to be strictly signed and hosted in the GAC so that you don’t have a problem with the version in the first place.

0
source

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

More articles:


All Articles