up vote 0 down vote favorite
share [g+] share [fb]

I would call thingy 'C' a folder, but how should I refer to thingies 'A' and 'B'?

The screenshot beflow is from the Visual Studio Source Control Explorer IDE.

TFS menu

link|improve this question
feedback

3 Answers

up vote 3 down vote accepted

I always refer to such things by their name (as in "Go to TFS, Customer Tools, Database").

I suppose TFS doesn't really need a name (it's the TFS root - seems self-explanatory to me).
Customer Tools looks like what other SCM systems call a "project", so unless a TFS guru says different that's what I'd call it.

link|improve this answer
I'd call it the 'root', but see also: 'depot' (Perforce) - 'repository' (cvs/subversion/git) - 'project' (Mercurial, though it looks like the 2nd level is a project in this sense, as @voretaq says, so you might want to choose one of the others...) – SmallClanger Jun 24 '11 at 15:10
Yeah, I think root and project sound right. Thanks guys. – Buh Buh Jun 24 '11 at 15:47
feedback
up vote 1 down vote

For me I typically go for what they represent inside of Team Foundation Server. For example "A" is a Team Collection (or Collection for short), "B" would be a Team Project (or Project for short), and "C" could either be a Folder or Branch.

So in the example you have above, I would say go to tfs Collection, CustomerTools Project, and the Database Branch.

link|improve this answer
feedback
up vote 0 down vote

I've seen this button on the Team Explorer window which suggests that thingy B is indeed a Team Project.

ThingyB

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.