TFS - So what goes into Version Control and what goes into Project portal lists?
What's the difference?
We can either store the documentation in the Team Project SharePoint site, created as part of the normal team project creation process. SharePoint offers extensive documentation lists and version support out of the box, with an easy browser user interface that most users are acquainted with, or via the Team Explorer.
Alternatively Team Foundation Version Control (TFVC) allows us to pack documentation into the TFVC source control database, whereby access is via the TFS source control explorer in Team Explorer or products such as TeamPlain.
So where should documentation go ... choice = decision!
Documentation
Well, looking at a recommended Team project source control structure, we notice the Documentation node under the main, in many cases under the development and production trunks as well.
We typically advise teams to store high level documentation that is specific to the project, such as project plans, conceptual requirements and customer correspondence, in the team project SharePoint portal.
Release specific documentation, such as users manual, release notes, bug fix description reports and detailed design documentation we typically store in the TFVC repository.
This, however, is how we see it and is not a hard and set rule!
Allowing 'more stuff' than just the default to enter TFVC
If you need to expand the extensive list of file types supported by TFVC on the specific TSF server, select the Team Foundation Server Settings, then Source Control File Types. The following is an example screen shot...
Select ADD and add your new file type. You will have to indicate whether multiple checkout and merging is supported for the file type ... typically you should avoid selecting the merging option for non-source files, i.e. large VM or installation file types q;-)
Summary
To summarise and 'emphasise' ... there is no standard to guide you to make the right decision. In fact, the guidance and best practice, is to investigate both repositories and to define a process that suits your organisation and your project team.
In essence, we are once again saying that you must make sure that TFS, TFVC and SharePoint is structured and used to guide and assist your team!