26.04.2015 Views

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

• Version Control XML – This process definition file is named VersionControl.xml and is<br />

located in the Version Control folder in the process template folder hierarchy. It defines a<br />

team project’s initial version control security permissions, check-in notes, and whether<br />

exclusive check-out is required.<br />

o Check-in Notes – Specify whether to include check-in notes or not. Check-in notes<br />

are provided by the developer when code is checked in to describe how, or if, the<br />

code changes are related to team processes. For example, a check-in note can indicate<br />

if the change was part of a security review, and can include details about the changes<br />

relative to the security review.<br />

o Exclusive Check-out – Used to control whether multiple users can check out a file at<br />

the same time.<br />

o Permissions – Defines what actions security groups and individuals can perform on<br />

items under version control.<br />

• Reports XML – This process definition file is named ReportsTasks.xml and is located in the<br />

Reports folder in the process template folder hierarchy. It defines the team project's initial<br />

reports.<br />

o Reports Site – The reporting site has a link to it, labeled Reports, on the project<br />

portal home page.<br />

o Folders – You can create folders on the reporting site. The folder(s) you create will<br />

appear on the project site and under the Reports folder in <strong>Team</strong> Explorer.<br />

o Reports – Used to add reports by using the .rdl files<br />

• Groups and Permissions XML – This process definition file is named<br />

GroupsandPermissions.xml and is located in the Groups and Permissions folder in the<br />

process template folder hierarchy. It is used to define the team project’s initial security<br />

groups.<br />

o Groups – Used to specify a new TFS security group.<br />

o Permissions – Used to define permissions for each group you specify.<br />

New <strong>Team</strong> Project Wizard<br />

You use the New <strong>Team</strong> Project Wizard to create new team projects. The wizard uses the plugins<br />

and the XML process definition files to create the project.<br />

Customization Approach<br />

To customize a process template, perform the following steps:<br />

1. Review the process templates provided by TFS and choose the one that most closely matches<br />

your organizational process.<br />

2. Download the chosen process template.<br />

3. Customize various components of the process template.<br />

4. Upload the customized template to TFS.<br />

5. Verify that the changes suit your process requirements.<br />

This core approach is used as part of the following solutions for customizing the process<br />

templates:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!