Team Foundation Server - A programmer's guide
- by Filip Ekberg
In addition to my Previous topic on
How to use SVN, Branch? Tag? Trunk?
I would like to get in-depth on how a programmer should/could use TFS.
The things that are most interesting to me is not how to set up the server, rather how you use it on a daily basis. In the area of software engineering where your responsibility not only lies on code but achitecture, documentation and other fields, you need to have a collection of your work, prefferably on the same place.
So these are my point of interest which I would like to get more knowledge about
How would you strucuter a TFS Workspace / Project to support lots of different customers / projects and maybe different projects per customer?
Splitting up the folder strucutre on the above project into different pieces such as, Code, Documents - Architecture, Requirements and other, what more could there be and what would be a nice commonly used folder structure?
An easy to browse repository; Again the folder structure here is important however this point is more aimed at different Explorers for the repository, not only the built in Team Foundation Explorer.
These are just a couple of the points that I would like to know more about, suggestions on Beginners guides, in-depth guides and links covering the above would be very much helpful, please feel free to add other important knowledge-points to this as well.
