TFS (Team Foundation server) agile use tutorial (2): Source Code Management

Source code Management

A folder is usually used to improve the weight process. There are various specifications and document templates in the folder,ISO9000So,RUPThe same is true,CMMThis is especially true. Most people will not be stunned when they see so many things, but the consultant will encourage you to tell you that this is a training framework and is a good product. When you have mastered these things, you will be able to understand the vast majority of things, then begin a long learning process. Newbie? This isForSenior position.

Agile development:CodeIs the most accurate document, a software can save everything, but code is indispensable. A project team can have no project manager, testers, or even only one person.ProgramMember. Now, as long as you can write code, you can start agile development immediately. Isn't the Threshold High? This is the software process closest to our programmers.

1 TFs 2010 getting started

TFS 2010After the installation is complete, click the following link to enter the door:Visual
Studio Application lifecycle managementGetting started

1.1 connect to team Foundation Server

1.2 create a team project

1.3 Add the solution to source code management

1.4 check in

Let's take a look at4Now you are getting started.

 

2. Source Code Management Resource Manager

Next, open "Source code management", which is the door to the crowd, CMM The document template set is just a bulky large package. Practice " Check in " , " Check out " , You can use TFS To work. It seems that some people use TFS It's a pity that it is only used for source code management.

 

3. Manage the Workspace

3.1Edit Workspace

Next, open the workspace, add or edit the workspaceTFSMap the server to a local folderD: \ ProjectsAfter confirming, the system will prompt you, "the workspace has been modified, whether to update the local workspace", select YES.

 

3.2Local Workspace

 

Yeslocal WorkspaceD: \ ProjectsDirectory structure. Each folder is mapped to a team project, which is exactly the same as the Team Project on the server. In this way, different projects are separated, and the results and process files of different projects are put in different project folders. Do not place them on the desktop, my documents, and the root directory of the logical drive disk. In addition, do not include irrelevant files in the team project. One of the secrets of agility is simplicity.

 

 

3.3Team project directory structure

The Team Project root directory contains three main directories:

NO.	directory	description
1	data	data
2	documents	documentation
3	Source	Source code

 

Software=Program+Data+Document. Isn't that what our software engineers understand? Let those high theories fall into practice as part of our practice.

 

4. Change set

4.1History

Select "Source" in "Source code management resource manager", and click the history record on the toolbar. We will see all the Change sets in the "Source" directory. These Change sets are the results of our daily check-in automation on TFS, which does not require the CMM processEntering such a form will not burden us. Even if we write a brief comment, we get used to it. You know, our goal is to reduce the pressure on programmers, not the pressure.

 

4.2Change set details

Now let's take a look70Number change set details, we see that this change is added with a file"Loadlayercommand. CS".

Right-click to view what is written in this file:

 

4.3Find change set

Open the "Find change set" interface. We can perform combined query by user, file, date, and other conditions. Yes file query"Loadlayercommand. CS"Change history to understand its development and restructuring.

 

4.4Check-in principles

The change set is generated by the check-in, so each check-in is treated correctly. Messy code will certainly lead to messy Change sets. For more information about how to write concise code, seeAgile Software Development: Principles, models and practices, reconstruction-Improve the design of existing codes and other books. For new users, try to use small changes when checking in. Do not check in multiple files with a single responsibility, for example, "importtxtfilecommand. CS "and" exporttxtfilecommand. CS "should be checked in separately, even if you write in the same file" mainform. CS "methods" importtxtfile () "and" importtxtfile () "are also checked in separately. Why? This is because we will generate work items from the summarized change set. If you check in a change set with a very high Coupling Degree, we will not be able to summarize it.Positive work plans are not easy, and reverse work summaries are much easier. Well, let's talk about it today. At least the work item is very close. The next article will discuss how to improve the ability of the work plan through work summary.