TFS Installation and Management

Installation

Tfs:visual Studio 2010Team Foundation Server

1.1. TFS Installation Scenario:

TFS offers 7 installation options for different application environments, most commonly used in our actual applications: Installing TFS on a single server. Since this is very common, only the installation method for this scenario is described.

1.2. TFS Installation Environment:

Memory: 2G or more

Processor: 2.4GHZ or more

System: Windows2003 windows2008

1.3. TFS Installation Components:

IIS 6 or IIS7 (Installation reference: TFS Environment build--iis installation)

Requirements:

1. Verify IIS 5.0 isolation mode is not used
2. Verify that IIS is not using FrontPage 2002 Server Extensions
3. Verify that IIS is using ASP.

SQL Server 2008 (Installation Reference: TFS Environment build--mssql2008 installation)

1. Use SQL Server Configuration Manager to verify that the Windows service is running
2. Use SQL Server Management Studio to verify the connection to the instance of SQL Server

Sharpoint (Installation Reference: TFS Environment build--sharpoint installation)

1. Verify that the administration site and the default Web site are running, and that other computers on the network can access them
2. Verify that the default Web site uses recommended authentication
3. Verify that the newly installed SharePoint product has a WEB application
4. Verify that Microsoft Office SharePoint Server 2007 is configured for panel compatibility

1.4. TFS Installation:

Microsoft Team Foundation Server 2010 Installation

Source Control Explorer

1.5. TFS Configuration:

Use standard configuration

1. Click Standard Single Server, and then click Start Wizard. The Team Foundation Server Standard Configuration Wizard appears.
2. Read the Welcome screen, and then click Next.
3. In user account, type the name of the service account (Wssservice) that you want to use.
This account is also used as a report reader account to create reports (TFSREPORTS).
In password, type the password for this service account, and then click Next.
4. Check the information, and then click Next.
5. The wizard will verify your configuration.
6. Click "Configure".
7. The wizard applies the configuration settings.
8. Click "Next".
9. Click "Close".
10. Click "Close".

1.6. Precautions

For the server's machine name, you must complete the modifications before you install TFS, or if you modify the computer name after you complete the installation, some services in TFS will not function correctly.

If Reporting Services does not install correctly with SharePoint before you install TFS, TFS does not automatically configure the associations for those services, and subsequent use of manual configuration will be complex and have a low success rate.

The VS2010 is installed on the server side so that it can be configured with its clients after completing the TFS installation and has the highest permissions.

The server is estimated to take 3-5 hours from bare metal to the installation of TFS.

Management

2.1. Project Structure

TFS has a concept called a project set for project management, so that you can create a collection under which the related projects are created.

The application scenarios are:

1, the enterprise can create a project set according to each project group, the project of each project group under own project set.

2, a large project contains a number of small projects in the management mode.

2.2. Create and delete items

Open VS2010 team Manager, click on the project Set right button, action.

Then, depending on the wizard, fill in the project name, whether to create a portal site, whether to use the new source control, and so on, and finally TFS will automatically help you create the project you set.

To remove project management, open VS2010 Team Explorer, right-click the project, and then select the action:

Note: The deletion of the project information here does not automatically delete the portal site, the need to manually delete, delete the way see the following chapters.

2.3. Permissions Configuration

2.3.1. Permission Description

2.3.1.1. Permission Associations

TFS's permissions are associated with the operating system's user or domain, and TFS is a rights management support for database accounts, operating system accounts, and domain accounts. TFS, which is commonly used under 20 people, is recommended to use the operating system directly for easy and simple accounts. When a team of more than 20 people or more, it is recommended to use the method associated with the domain account.

2.3.1.2. TFS Permissions Structure

The permissions structure of TFS is hierarchically managed based on the project set, project, and content. The lower layer overrides the upper-level permissions configuration.

2.3.1.3. Permission Groups

TFS has a default group at each permission level, and you can modify existing groups or create your own groups.

The following groups are defaulted under the project set:

Under each item, the following groups are defaulted:

Each permission group can include different members, with different permissions for operations.

2.3.2. Project Permissions Configuration

The project's permissions configuration includes project-level, source code, region, team query, and generated permission control.

Project-level permissions control, just to control whether users have access to the project, as well as the project set. Project-level access does not represent permissions with source code, zones, and so on, and requires one by one configuration, but TFS generates 4 permission groups by default, and there are default configurations for different content, typically only members of those groups need to be configured.

To accommodate the default permission group, add members as an example:

Click VS2010 Team project Manager, right-clicking the team project, action:

The following dialog box appears, selecting the Participant click Properties:

In the following dialog box, select Add from Windows user or group, before the new pop-up box is entered in the system-created user name.

Note: For simple configuration, create an account for everyone participating in TFS Management on the operating system, and each subsequent user will log on to TFS based on the user name/password of the current operating system.

Once the operation is complete, the configured user can access TFS and work on it. The default four groups have different permissions, for example, the visitor has the fewest permissions, the user in the current group has the fewest permissions, and the Administrators group has the highest permissions.

When a user belongs to both the Administrators group and the Access group, the current user has all the permissions of the Administrator plus the visitor.

If you need granular permission assignments, you can create your own user groups for management. However, the newly created user group needs to assign permissions to the source code, region, team query, Generation, and so on, and then join its members.

The permissions of the source code can be divided according to the directory.

The permissions for a zone are primarily control over the work item content, such as whether a work item can be created, whether the task can be closed, and so on.

Team queries, mainly control the permissions of some of the customized query information.

Generated, primarily for permission control of the build operation.

2.3.3. Reporting Services Permissions Configuration

The permissions for Reporting Services are independent of project management permissions for TFS, and are set up in the following ways:

Open the report Configuration Manager, select the Report Manager URL tab, and click its URL to enter the following Web site:

Click TFSReports to enter the subdirectory, select the set of items you want to configure permissions for, and then select the items to go to subdirectories.

Then click on the properties for a few clicks:

Once you click Security, click New Role Assignment,

The following page appears:

Group or user name must enter the current operating system under the group name or user name, the contents of the permissions are checked according to the actual situation, and finally click the OK button to submit the completed operation.

2.3.4. portal Site Permissions Configuration

The permissions of the portal site for TFS are also independent of the permissions of the TFS project and need to be set separately. The Setup method is as follows:

In the server's VS2010 team resource management, select the project under Project set, right-click the display project portal and the following site appears:

Click on the link in the Red Circle-site action, select Site Settings in the dropdown box, and the page appears.

Select people and groups, and the page appears.

Click the New button and the new user page appears.

User/user group, you must fill in the user or group in this operating system, you can click Check Name to confirm after entering. The grant of permission is checked according to the actual situation, and finally click OK to complete the operation.

2.4. Work Item Management

Once a work item in TFS is created, it cannot be deleted. The main consideration should be that Microsoft feels that since there is a plan to add work items there must be a need to provide modifications, but no longer the UI page provides a way to delete. If you do need to delete a work item, you can delete it by using the command line. The operation is as follows:

Enter command-line mode,

Enter the command:

CollectionName: The name of the project set, which requires HTTP and port.

Idnum: The ID number to delete.

3. Template customization

3.1. Methods

TFS supports customization of work items, process templates. A secondary tool, Microsoft Team Foundation Server, is recommended for Power tools. After installation, you can export the template definition file directly from the server and import it directly to the TFS server after saving. If you do not use a tool, you can do it from the command line (not recommended).

After you install Microsoft Team Foundation Server Power Tools, this feature is added to the VS tool:

3.2. Work Item

Customize the work items, you can customize bugs, tasks, and so on, or create a new work item. This article explains how to modify the default task work item as an example.

Using Microsoft Team Foundation Server Power Tools, do the following:

Pop-up Select Type dialog box, select Project set, Project, type after Popup interface:

Fields is the field that defines the occurrence of a task work item.

Layout is the field layout that defines the dialog box that creates a work item popup.

Workflow is a workflow that defines the changes and actions of work item state.

3.2.1. Field definitions

The template can add a new field definition, and the information for the field can be referenced using the tool:

Select the custom definition you want to add from the work Item Field Explorer, depending on your actual needs.

3.2.2. Layout modifications

A template can define the location of fields in a window, and can also be checked using the preview feature.

Create a new control at the specified location, and then select Filedname and type in the Properties window.

Here you can choose the new type or the existing type that you just imported in the previous step, type specifies the control, which can be a drop-down box, a date selection or text, and so on.

3.2.3. Workflow Modifications

Templates also allow custom workflows to be modified with the VS designer and the toolbox controls.

3.3. Field mappings

In TFS Export to project file, you can customize the fields of TFS to be mapped with peoject fields, as follows:

To download the mapping file:

Project set name, project name enter according to the actual situation, the map file name can be customized.

When the download is complete, use the editor to open the XML,

You can add a record that corresponds to the field properties in the Work Item field Explorer, and to the fields in project.

Upload to TFS using instructions after you complete the modification:

TFS Usage Guide

1. Project planning and Tracking

Often a lot of friends complain about the fearless plan in daily chats because the plan will never catch up with the change. Indeed, the plan is not up to the change, but you don't plan, you never know what you should do, when you do it, and while it changes, you can tailor things to the original plan and change the positioning of the changes, while controlling the evolution of change.

1.1. Use project to develop a program plan

Create a new project file, or open the project-document-project management-develop project plan. xlsx file in the TFS Team Explorer dialog box. The files that are open at this time are an empty project file, which you can plan for planning in this file.

Select the Team tab of Project, click Select Team Project,

Then select the item you want to publish in the dialog box that pops up, and project will default to the TFS-related heading fields and feature options.

The job to do now is to specify your project plan in project, as usual. Roughly as follows:

STEP1: Develop an iterative plan and a general direction work plan for this iteration.

STEP2: Lists all the work of this iteration, prioritizing and dependencies.

STEP3: Estimate the content, start time, end time, resource, and estimated duration for each work task.

After the plan is complete, you need to synchronize to TFS so that other team members or team leaders can get the task and decompose it in more detail. Syncing is simple, just click the Publish button under the Team tab.

Note: If the completed project plan has an exception or does not meet the requirements in the synchronization, the wrong item is automatically ejected and a description of the proposed modification is displayed.

Once the release is complete, you can inform the team leader to make a more detailed division of the plan.

In order to allow members to quickly navigate to their tasks, a team query is required, which is typically done by the TFS configuration Administrator. Actions are as follows: Go to Team manager, select Project-Team query, right-click Add, Action

After the dialog box is popped, configure the condition:

When the settings are complete, click Save and enter any name (suggested "My work Items").

Next, each team leader logs in to Team Explorer, clicks on work Items-team queries, selects the query you just created, and VS lists all the work items that belong to me.

If you accept a plan in VS, you can plan directly with the various actions offered by VS, but if you want to be able to plan and import it in project, it's no problem, it's easy to do.

After the query results, click the button:

Here you can see that you can export to Excel, project, we choose to compare Common project, select will automatically create the project file and refresh the data into the file.

Note: Project editing here is a completely different concept from how we usually modify a project file together.

You're done, the rest of the work is to specify the schedule in project and then publish to TFS using the Publish feature.

Task refinement After the completion of work, is to each member according to the assigned task to work.

1.2. Information Association

Activate the task state (this process can be defined by itself, which is just as a description of the situation), and then start implementing the requirements of the task, and then go back to TFS to change the task state to "resolved" and then to the next task, and so forth.

But here's a point, the use of the above is not very good, TFS provides a task record is not only to record the completion status of the task, but also associated with a lot of information, to see the New Task Creation dialog box:

Detailed information can be how the task is done, and what problems encountered in the record;

All links can be the source code of the migration set to associate, know which code the task to modify;

Attachments can upload some other content about this task, documents, etc.

1.3. Project Tracking

With the above operations and the accumulation of data, the overall tracking of the project is no longer a difficult thing to do, easy to open the query of TFS, select the unfinished state of the project, or the completed project, or other dimensions, can be located in the current project situation.

Of course, TFS also provides many reports to analyze from different angles, providing the project manager with an analysis of the status of the project, which can be customized for each of these reports and queries.

2. Source Code Control

A lot of people using TFS are just using TFS's source control features, here's a quick introduction to source control features that I think are very useful and how to use them.

2.1. Checkin Strategy

The so-called checkin strategy is that every time you perform a checkin operation, it checks to see if your request meets the requirements according to the defined policy, the most commonly used policies that must be associated with the work item, and the checkin must fill in comments, and so on.

This allows you to customize or use the default provided policies based on the characteristics of your team project.

The operation is as follows: Select Project Right-click Source Control,

Select the migration policy in the pop-up window and select Add to see the policy currently provided by default:

For the import and use of custom policies, due to the length of the article is not discussed in this paper, detailed can be consulted Microsoft MSDN.

2.2. Multipoint Checkout and merge modifications

TFS Source Code Manager runs multiple people together checkout a file, modified checkin will automatically help you to merge files, when there is a conflict in the time to provide an editor to choose how to modify, personal feeling more useful. The description cannot be provided temporarily because there is no checkin conflict code.

Here is a brief description: When the same file is checked out by 2 people, if 2 people modify the same file different location, the code Manager automatically help you merge; If you modify the same place at the same time, the conflict editor will let you choose which version of the person to use.

2.3. Marking tags

Tag is to make an identity for the current source code status, so that you can later call this version of the source code. General Application Scenario: Release version.

Action: Right-Select the source code Manager's directory, pop-up menu, select the App tab,

3. Document Management

The documentation directory under the project in Team Explorer can provide the relevant management functions of the document, and the documents in our project can be uploaded to this, as a way of document sharing and document versioning.

I use WINDOWS2008R2 when found unable to directly open the Word document and then click Edit to check out, you must download the entire file each time, after the completion of the complete file re-upload, Google search for the relevant content seems to be a bug.

4. Build

To use the build service, you must make some configuration to the server.

Open the TFS Management Console, choose Build configuration, you need to create a new controller and proxy, I created the basic use of the default properties.

The generation of TFS has not been used very well and has not been successful many times and may be primarily related to the structure or configuration of the project. New Generated method

This Part I always wanted to be able to modify the build process template so that TFS builds up after the VM can start a virtual machine to restore a state snapshot, then automatically deploy, and then run the automated test to submit the report last. (still in the study)

Normally, the definition of the generated content has triggers and workspaces, and other retention defaults are basically no problem, and TFS builds and unit tests based on the workspace you specify.

5. Using Process templates

5.1. Work Flow

5.2. Using Agile templates

Work items that are provided by using the default agile template

The process is as follows: first define the iteration plan, define the user story description for the current iteration, then divide the various subtasks that implement the user story, and design the test cases, and test feedback bugs after each task is completed. In an agile stand-up meeting, the questions raised can be recorded by the problem work item.

5.3. Template Customization Recommendations

The work item template that TFS provides by default can be modified as follows:

The start time and end time are moved from the default tab to the first item, which makes it easy for us to make a plan when entering or viewing the task when the first visual is seen. For the start and end times because the default configuration is not to refresh data from TFS to project, I feel that in order to maintain the consistency of TFS and project, it is recommended that you remove publishonly=true when mapping. Similarly, the end time also exists for this issue.

We are accustomed to planning time and actual time, I think the start and end of TFS as a planned time, and activation time, resolution time is the actual start and end time of this task, so it is more secure. However, if you do this, you must standardize your operating habits and activate the task each time you start a task, instead of completing the TFS operation after the final task is completed.

TFS Installation and Management