Geek Answers Handbook

How to handle common projects in the Team Foundation server source control structure

After you read the Team Foundation Server Source Code Management Framework , which I came across with a few questions, it comes to my mind that I am wondering if anyone can comment.

I have several components that make up the project I'm working on. I have smartclient, webservice, a proxy server for a web service that uses smartclient, a daemon and a general utility that is used in both smartclient and webservice. Each of the components is associated with the same work project.

I structured my source tree so that each component was independent - in other words, each component (smartclient, webservice, daemon, proxy, common utilities) has its own trunk and its own solution file, because I want to be able to release each component whatever. For components that are used by other components, for example, in the case of smartclient using a proxy server and general utilities, I created releases that are processed like any other third-party library (binaries referenced instead of projects). Can someone confirm that this is somewhat better, and if not, how should it be done otherwise?

I created releases of my components using the tfs assembly, and I wonder where I should put the releases, if somewhere except in the assembly output directory where all the tfs assemblies are located. Should I possibly check them (for example, proxy builds that smartclient will use) in TFS along with any other third-party libraries, and then deploy the release builds where they should be used (for example, the dlls proxy branch to a directory smartclient lib)

+3
source share
2 answers

We have created the \ common share on the TFS server, which contains subfolders corresponding to each major shared project. For example:

\\common  
    \sharedproject1
        \v1.0.0
        ...
        \vN.0.0
    ...
    \sharedprojectN

\ \ sharedprojectN\v Mmn

.
(, " " ) , .

, .
(, " " ), , (, ).
, \release.

, .

+2

, , " ". Team Build . "Replicator Dependency", .

, , . , , : A) B) .

( XML), "" .

+1

More articles:


All Articles