Is there any guidance about workspace naming and workspace mapping in TFS (2010) ?
+1
A:
I'm not aware of any specific guidance on this, but after a couple years, we've primarily settled on a single workspace mapped to root $/. We've been operating like this for probably a year with 80+ developers, and haven't seen much of an issue.
In my opinion, this is valid, as is the idea of one workspace per Team Project, as long as you don't have a whole lot of Team Projects to deal with.
Robaticus
2010-07-06 14:07:32
We've been doing the same thing here and it's been working well since 2005.
Ryan Rinaldi
2010-07-06 19:00:05
Patrick Peters
2010-07-07 06:41:05
I don't know if there needs to be one, except for-- make it easy to differentiate. I currently have WorkLocal, MergeSpace, and ComponentUpgrade. My main space is WorkLocal, with the other two being used for a couple of special efforts that are going on.
Robaticus
2010-07-07 14:01:52