Many customers have told me about the need to automatically create the document structure of the origin code base when creating a team TFS project, such as a folder that resembles the following structure:
<teamProject>
|-Development
|-MAIN
|-BUILD
|-SOURCE
|-TEST
|-releases
One, Team Foundation Server 2012 Scenarios
By analysis, the team Project process template for TFS does not support the pre-defined source directory structure, but fortunately, Visual Studio 2012 supports creating a branch in the process of creating a team project. We can use this function to achieve the above purpose, the concrete way is this:
First step: Create a team project, create a directory structure for the project in this team project, as a template project
Second step: In the subsequent new project process, the above project as the source branch, create the directory structure of the source code library. The following is a description of the operation process:
Figure-New team project
Figure-A selection process template
Figure 3– Setting up SharePoint Integration
Figure 4– Select an existing project as the source branch of the new project
Figure 5– Complete the creation process
Ii. Team Foundation Server 2013 Scenario
The above scenario is not a problem in TFS 2012, but after upgrading to TFS 2013, you will find that Microsoft canceled this feature, the new group project has no option to develop the source branch, can only choose TFVC or git (such as)
However, the rationale for the above scenario can still be exploited. After you create a team project, you can create a branch in the new team project, and then copy the branch structure in the template project, by using the template project as the source branch.
article source:Http://www.cnblogs.com/danzhang Zhang Hongjun
automatically establish the folder structure of the code base when you create a TFS team project