Team explorer tutorial)

ArticleDirectory

• I. Installation of team Explorer
• Ii. Use of team Explorer

I. Installation of team Explorer

Attach a CD or image file containing vs team explorer to the optical drive (take the image as an example) and run the installationProgram, Follow the prompts to complete the installation.

Note:

1. Different images are different. If it is an image file that only contains team explorer, you can run the installation program and start Installation directly. If it is an installation disk of vs team Foundation server, you are required to choose what to install, select "team resource manager" or "Team Foundation server ". The installation path is not optional. It is the vs installation directory. Make sure that the partition space is sufficient.
2. If you have installed vs 2008 SP1 before, you will not be able to open or add a work item after installing team Explorer (see the following section for instructions on work items). solution: re-install vs 2008 SP1. Since it is invalid to directly install SP1 again, we recommend that you first open "add or delete programs" to uninstall SP1-related items, and then install SP1, or, install team explorer after uninstalling it, And then install SP1.

Ii. Use of team Explorer

Note: The following uses the English version of vs2008 as an example. However, I try to describe it in Chinese (English. The title * below indicates that this part is operated by the Project Administrator. Other project participants do not need to perform this operation.

 

1. SetSource codeSource Control)

Choose tools> options. In the Options dialog box, select source on the left.CodeSource Control Branch, where you can select the source code control plug-in and select Visual Studio team Foundation server ". There are several sub-branches under the "Source Control" branch, where you can set the check in/check out rules and the proxy settings for connecting to TFs, you only need to keep the default settings.

 

 

Figure 1. Set the source code control plug-in

 

Figure 2. Set check-in/Checkout rules

Figure 3. Set proxy

 

2. Set team projects

Choose View> Team explorer to open the team resource manager. Click "add existing Team Project" in the upper-right corner to open the connect TFs dialog box and click "server ..." Button to open the "Add/Remove TFS (Add/Remove team Foundation server)" dialog box, click "add ...)" Button to open the Add TFS (ADD team Foundation server) dialog box, enter the machine name of the server where TFs is located, such as the hust-709, at TFs name (Team Foundation server name. Keep the default connection details. OK. The verification window for connecting to the server appears. Enter the domain user name and password that the TFS administrator assigns to you. In this case, the "connect to team Foundation server" dialog box shows a list of projects authorized to the logged-on user. Select your project and click OK. In this case, "Team Explorer" provides items related to the items selected. The specific meanings of each item are described later.

 

 

Figure 4 and 5: Team explorer, connect to TFs dialog box

Figure 6: Add/Remove TFs dialog box

 

Figure 7: Add TFs dialog box

Figure 8: connect to the TFS server verification window

Figure 9: select a project that has been authorized to the user

Figure 10: Team Explorer

 

 

3. Create a Team Project (*)

Choose File> New> Team Project to open the new Team Project Wizard. Enter the project name here, for example, "test", click Next, and select the management template. By default, you can set the team portal website title and description, this part can be left for later settings in the portal. Click Next to set the relationship between the team project and other projects. Is this independent? Or is it a branch of a project? Here we select the first item. The next step is to summarize and click Finish.

Figure 11: Enter the project name

Figure 12: select a project management template

Figure 13: source code control settings

Figure 14: Project added

4. Add a solution to a team project (*) 4.1. Add an existing solution

Open the existing solution, right-click the solution, and select "add solution to source control )", in the displayed dialog box, select the Team Project (TEST) You just created to confirm. After that, you can see a yellow plus sign in front of the project and file displayed on Solution Explorer, indicating that the current item is added to source code control. Now the solution has been added.

 

Figure 15: Select Add solution to source contro...

 

Figure 16: select the Team Project to add

Figure 17: added Solution

 

4.2 create a solution

Choose "file"> "new"> "project )", in the new project dialog box, you only need to check "add to source control" in the lower-right corner. Other operations are the same as above and will not be repeated here.

Figure 18: new project dialog box, select Add to source control

 

 

 

5. Check in the code

The so-called check-in code refers to modifying the code locally (including adding projects, adding files, modifying code, modifying solution settings, and other operations that change the controlled files) reflected on the server, so that other team members can immediately obtain the latest source code.

Right-click the file, project, or solution to be checked in and choose check in. In the displayed check in dialog box, enter description (comment ), select the items to be checked in (all the modified items and types are listed here, not just the current item you opened .). In the work items section, you can set the work items that have been checked in here (for descriptions of work items, see the following section ). In the "check-in notes" section, you can set "code reviewer", "Security reviewer", "performance reviewer", and other information related to this check-in. Click "check in" to complete the check. Of course, it is possible that two people modify a file at the same time, which will cause code conflicts. This part will be introduced later. Now let's look at solution manager. We can see a small lock before each item, indicating that the item has been checked in ).

It is recommended that you obtain the latest version before checking in, and check in after ensuring normal compilation and running.

Figure 1: Right-click to select Check In

Figure 2: Check In dialog box 1

Figure 3: Check In dialog box 2

Figure 4: Check In dialog box 3

Figure 5

6. Obtain the source code

After adding this project to other participants of the project, you can obtain the project source code using the following methods. In "team resource manager", double-click "Source Control" to open "source control Explorer". The projects that the current user can participate in are listed here, black indicates that the project has been added to the team resource manager. Right-click the project or its subprojects and choose "Get latest version )", if you have not obtained the source code before (in essence, you have not created a workspace, so you will talk about it later), a dialog box will pop up to select the folder to save. You can download the project source code from the server to the selected folder. If you want to obtain a previous version, right-click it and choose get. In the get dialog box that appears, select a class in the version section, for example, the date, Changeset, the latest version, and so on.

Figure 6: Double-click source control

Figure 7: Get the latest version

Figure 8: select the folder to save

Figure 9: Get a specific version

 

7. Manage a workspace

Workspace, well, this is not a good explanation. I think it is like a place where you work. You write code and manage code in this particular place. Well, you can understand it yourself. Okay, no explanation. Let's talk about how to operate it.

7. 1. Create a workspace

Menu File> source control> Workspace ...), The Manage workspace dialog box is displayed. The existing workspace is listed here. If it does not exist, click Add. Here, you can set the workspace name, logon User Name (owner), and computer name (computer ), description (comment) and working directory (working folder), click the button in the source control folder cell, select a project in the pop-up dialog box, and click the button in the local folder, in the pop-up folder, select the local code folder and click OK.

 

Figure 10

Figure 11: Manage a workspace

Figure 12: Add a workspace

. Edit Workspace

In the space dialog box (manage workspaces), select the workspace to be edited and double-click or click Edit to open the edit workspace dialog box. You can make some modifications here. Note that the working directory (working folders) contains a working directory (if it is in the same workspace) for each project you participate in. You can edit it, for example, if you change the local directory, the program will prompt whether to get the latest version or remove this project. The window will also pop up whether to get the latest version. If you click yes, the file in your original folder is gone.

7.3 delete a workspace

This part is not required.

 

8. Check out

Check out is like telling someone else that I want to change this file. You 'd better not change it, or there may be conflicts. If "allow multiple users to check out at the same time" is set, conflicts may occur. Of course, if there is no choice, someone else cannot check out after checking out. The specific settings are not discussed in this part.

The simplest way to check out is to double-click a file in Solution Explorer, and the first modification to it will trigger the check-out operation, this is the default setting. You can set this part in options. For more information, see team explorer tutorial 1. If Automatic check-out is not set, right-click and select "check out for edit now" to complete any operations. After the file is checked out, a red check mark is displayed in front of it.

A small profile picture will appear before a file or project that has been checked out by someone else.

Figure 13: Set check-in/Checkout rules

Figure 14: Select Check Out for edit now

Figure 15 files checked out by others

 

9. Lock

The purpose of locking is to prevent others from editing this file. Right-click the file you want to lock and select "Lock" to open the "Lock" dialog box, here, you can check which files are locked and the lock details. If you want to unlock the file, select unlock in the same way.

Figure 16: Select lock

Figure 17: Lock dialog box

 

 

10. Compare File Modification

A convenient and practical function provided by VFS is the comparison function. Through this function, you can know the difference between the current version and other versions (such as the latest version on the server, you can use this function to resolve code conflicts. It's easy to use. Right-click the file you want to compare and select "Compare" to open the "Compare" dialog box. You can select the source file and target file, and click "OK" to open a window, the target file and source file (such as the file you modified) are displayed in two columns, and the modified part is highlighted in gray. There are two buttons on the top to the Right to quickly jump between several changes.

Figure 18: Select compare

Figure 19: Compare dialog box

Figure 20: Comparison window

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

11. Undo local modification

With this function, you can undo the modifications that have not been checked in to the server. Right-click the file or project to undo the modification, and select "undo pending changes ...", In the displayed dialog box, select the file to be undone and click "undo changes.

Figure 21: Select undo pending changes...

Figure 22: Undo pending changes dialog box

 

 

 

12. Work Item

 

 

Work items, as the name suggests, are coming soon. Work Items include bugs, solutions, tasks, service quality requirements, and risks. Here we only discuss the most common bugs and tasks. Tasks are expected to be done, while bugs are unexpected. This is the simplest difference.

 

12.1. Add a task/bug

Right-click work items in team explorer and choose add work item> task/bug, on the displayed tab, enter relevant information and save the information to add the task or bug.

Figure 1

Figure 2: Add a task

Figure 3: Add a bug

12.2. view work items

In "work items" of "Team Explorer", expand "Team queries" and double-click "All work items ", open the "All work items" tab, where you can see all the work items in the project. Click any item to view the details below, double-click to view the work item in the form of a new tab, you can modify it. If you double-click "Team queries", a work item assigned to you is displayed on the open tab.

Figure 4

Figure 5: All work items

Figure 6: My work items

12.3. Close work items

When a work item is completed, postponed, or assigned to others, it should be closed in time so that other personnel in the team can know the progress of the entire project. To close a work item, you only need to open the details page of the work item, select "closed" in "status", and select the reason for closing in "reason, for example, if "completed", you can add instructions on this work item in "Description", "History", and other places. Save to close this work item. If you find that the work item is still unfinished, you can select "active" in "status", which will reactivate the work item.

The bug may be somewhat different, but there are more options, which can be completed based on the actual situation.

 

Figure 7: Disable a task

Figure 8: Disable a bug

13. Reports

The team explorer provides multiple reports for team members to understand the project.

To view a report, you only need to open team explorer and expand the report branch to view a series of reports provided by TFs. Double-click the report to view the response. For example, open "remaining work". Here, you can see the active, resolved, and closed work items, which are very clear. The following are some examples.

Figure 9: report list

Figure 10: remaining work

Figure 11: reactivate

Figure 12: Project speed

 

Iii. Conclusion

At the end of this series, TFS has many powerful functions. I just mentioned some common applications here. For the errors in this article, please point out. For more details, refer to msdn.

 

 

 

 

 

From: http://www.cnblogs.com/acen/archive/2009/05/04/1448750.html