Visual Studio Team System 2010 Team Suite:

• Visual Studio Team System Database Edition: The features that formerly released as Microsoft Visual Studio Team System 2008 Database Edition are now included as part of Visual Studio Team Development 2010.

• Visual Studio Team Explorer: The client application installs with each product in Visual Studio Team System.

For more information, see the Microsoft Web site: Visual Studio Team System Home.

Visual Studio 2010 Team Foundation Server:

• Streamlined Installation: You can install on client operating systems using an included version SQL Server Express.

• Flexible Installation Options: You can choose whether to use SharePoint Products or the reporting feature.

• Team System Web Access: Team System Web Access is automatically installed and configured when you install Team Foundation Server.

For more information, see the Microsoft Web site: Installation Guide for Team Foundation.

Plan and Schedule Projects:

• Schedule Work, Assign Resources, and Create Task Hierarchies:

  • Create task hierarchies and maintain task relationships in Team Foundation Server by using Office Excel and Office Project

  • View and modify dependent and nested, hierarchical relationships in a graphical view

  • Manage your product backlog and plan iterations with the new Agile Planning Workbooks that are defined for the new MSF for Agile Software Development v5.0. You can use the Agile Planning Workbooks to help load balance your team and track progress toward completing project iterations.

• View and Trace Relationships and Dependencies Among Work Items:

  • Track code defects and test coverage with increased integration of work item tracking with Team Test, Test and Lab Manager, and Test Runner. This integration includes the implementation of new types of work items such as Test Case and Shared Steps and associated link types that are defined for the MSF for Agile Software Development v5.0 process template.

  • View lists of related work items based on their linked relationships by using a direct link query

  • Collaborate more effectively within and across team projects by defining work item dependencies

  • Define one-to-many relationships by linking one work item to multiple work items with a single action

• Better Integration of Team System Web Access with Team Foundation Server: Create and update work items; create relationships among work items; view dashboards, reports, and build status; and accomplish most tasks supported by Team Explorer using Team System Web Access.

• MSF for Agile Software Development v5.0: The latest version of MSF for Agile Software Development provides a new set of work item types, link types, reports, and documents to better align with how agile teams work. For increased visibility into the progress of the project, built-in dashboards show if the bug count is growing or shrinking, and the rate at which bugs are being fixed, created, and closed.

• Organize and Manage Access to Team Queries: Create team queries and nested hierarchies of subfolders to contain team queries, and specify access permissions to each.

• What's New in Tracking Work Items

• For more information, see the Microsoft Web site: Agile Planning Tools In Visual Studio Team System 2010

• Creating Relationships Between Work Items and Other Resources

• Finding Bugs, Tasks, and Other Work Items

• What's New for Testing

• MSF for Agile Software Development v5.0

• Sharing Work Items and Queries with Team Members

View and Track Progress and Report on Your Entire Portfolio: You can identify problem projects and trends by using the following features:

• Customizable, Role-based, Out-of-the-box Dashboards: Quickly find important information about your assignments, status of your project, software quality, test progress, and build quality with one of the out-of-the-box dashboards. These dashboards are defined for MSF for Agile Software Development v5.0 and use features available with SharePoint Products.

• New and Improved Reports: View and track progress using one of the many out-of-the-box reports. Some of the reports provided include bug status and bug trends, build quality indicators and build summary, burndown and velocity, reactivations, remaining work, stories overview and progress, and test case readiness and test plan progress. These reports are defined for the MSF for Agile Software Development v5.0.

• Warehouse Database Views: Easily create Transact-SQL queries for your reports using the new views for the warehouse database. Unlike the tables on which they are based, these views are designed so that you can use them in reports, and they are less likely to change in new releases.

• Generated Excel Reports from Work Item Queries: Quickly create simple visual reports based on a work item query. This feature analyzes the query and creates reports in Office Excel that are connected to the SQL Server Analysis Services database.

• Dashboards (Agile)

• Reports

• The Warehouse Database for Visual Studio Team System

• Creating Reports in Excel by Using Work Item Queries

Office Client Integration:

• Maintain summary, subordinate, and dependent task relationships in Office Project for work items that are stored in Team Foundation Server

• Roundtrip predecessor-successor relationships from Office Project and Team Foundation Server

• Maintain format and formulas that have been added to Office Excel worksheets that are connected to work items that are stored in Team Foundation Server 

• Use the Undo function in Office Project for files that contain work items that are stored in Team Foundation Server

• Managing Work Items Using Office Excel Bound to Team Foundation Server

• Scheduling Tasks and Assigning Resources Using Office Project

Customize and Manage Work Item Tracking:

• Use the following new controls in work item forms to support the following scenarios:

  • Link filter: Control the set of link types that can be used to link types of work items. Also, you can specify the default column fields displayed for links in a work item form.

  • Hyperlink label: Attach a hyperlink to informational text or to a field label.

  • Standalone label: Provide informational text that is not associated with any field. Optionally, you can attach a hyperlink to some or all of the text.

  • Web content: Display content from a URI or HTML-based content within a work item form. Optionally, you can apply conditional actions based on the value of another field.

• Generate flexible reports and support increased integration across team projects by grouping types of work items by category

• Support specific traceability requirements by customizing link types

• Permanently remove items from the work item tracking database

• Controlling the Link Displays

• Adding Standalone Labels to a Work Item Form

• Displaying Web Content within a Work Item Form

• Grouping Work Item Types into Categories

• Customizing How Work Items are Related through Link Types

• Permanently Removing Work Items [witadmin]

Dependency Graphs and Architecture Explorer: Generate dependency graphs from source or compiled code to help you understand the functional areas and relationships in a system. Browse relationships in the code, and focus on areas of interest by using Architecture Explorer.

• How to: Find Code Using Architecture Explorer

• How to: Explore Code with Dependency Graphs

Code-Based Sequence Diagrams: Visualize the interactions between instances of classes by generating sequence diagrams from existing code. Communicate changes in the design by editing the diagrams.

• How to: Generate Sequence Diagrams from Code

Layer Diagrams: Visualize and define the logical architecture of your system on layer diagrams. You can organize classes, namespaces, code files, projects, and other artifacts in your Visual Studio solution into logical layers and describe their existing or intended dependencies. You can validate your code to keep it consistent with the intended design. You can include layer validation during check-in and build operations so that you can find dependency conflicts early and regularly.

• How to: Create Layer Diagrams from Code

• How to: Validate Code Against Layer Diagrams

Unified Modeling Language (UML) Diagrams: Model user requirements and describe the design of your system by using UML diagrams. Team Architecture 2010 supports the following types of UML diagrams up to the UML 2.1.2 specification: activity, component, class, sequence, and use case. You can also customize diagrams by using profiles.

• Developing Models for Software Design

• Modeling User Requirements

• Modeling the Architecture of a Software System

Integration of Model Elements with Work Items in Team Foundation Server: Organize the tasks for updating your system by creating and linking work items with model elements. This mapping creates a strong relationship between the parts of your system that are under development and the requirements they must meet.

• How to: Link Work Items to Model Elements

Extensibility for Models and Diagrams: Customize model and diagram elements, generate code and other artifacts from models, add commands to UML diagrams, and create tools to manipulate models.

• Extending Models and Diagrams

• Customizing Your Model with Profiles and Stereotypes

View Actionable Diagram of Merges: Starting from a file, changeset, branch, or work item, you can quickly retrieve a diagram that displays each merge of a changeset. You can see both where and when the merge occurred. You can also use the diagram to perform common tasks. For example, you can merge a changeset by dragging the changeset to a branch where the changeset is required.

• View Where and When Changesets Have Been Merged

View Actionable Diagram of Your Branch Hierarchy: This diagram can help your team members understand your team project's branch hierarchy, get detailed information about each branch, and initiate typical actions such as merges.

• View the Branch Hierarchy of a Team Project

Resolving File Conflicts in the Pending Changes Window: The Pending Changes window enables you to more quickly and easily resolve file conflicts.

• Resolve Conflicts between Two Files

View Merges in a File's History: When viewing the history of a file, you can see detailed information about each merge that caused changes to the file. This information includes the branch from which the merge came and the date and time of the merge. You can also drill down and view details about the changeset in which the changes were made.

• View Historical Data

Manage Labels: The new Label window gives you tools that make it easier to apply, edit, remove, and manage your labels.

• Use Labels to Take a Snapshot of Your Files

Rollback: You can use the tf rollback command to eliminate the affect of one or more changesets on an item.

• Run tf rollback /? at the Visual Studio 10.0 Command Prompt for more information.

Debug at Specific Points in Time with Historical Debugger: increases debugging productivity by reducing the time required to reproduce and diagnose an error in your code. Unlike the standard debugger, which shows the state of the system at a point in time, captures and records what the application does when it is running on your server. When an error occurs, you can view the state of the system at any time from the start to the point of the error.

Additionally, because testers can record a historical debugging session in the environment where a bug occurred, Team Development reduces the chance of not being able to reproduce a bug.

• Debugging With IntelliTrace

Manage Database Change: The features that formerly released as Visual Studio Team System 2008 Database Edition are now included as part of Team Development. As a result, you can apply the same life-cycle tools to your database code that you apply to your application code.

• Managing Database Change

Support Third-Party Database Schema Providers: You can add third-party database providers to manage changes to database servers other than SQL Server. The specific feature extensions depend on the database providers. For example, other database providers might support different types of database refactoring operations.

• Specific information about third-party database providers will be forthcoming. These providers are not included with Team Development and must be installed separately.

Improve Code Quality With Code Analysis Tools: Focus on your critical quality goals by using managed code rule sets to organize code analysis rules and check-in policies.

• Enhancing Code Quality with Team Project Check-in Policies

• Analyzing Application Quality by Using Code Analysis Tools

Keep Tests Up-To-Date with Test Impact Analysis: You can see a list of both manual and unit tests that are affected by your target code changes by using Test Impact Analysis. As you run those tests, the test list adjusts to show only the remaining tests. Additional code changes adjust the list of unit tests, as do tests that are running on the server.

You can also predict many potential check-in problems that would otherwise have gone into your build and remained undetected.

• Identifying Code Change Impact on Tests

Set up Virtual Staging and Test Environments: With Lab Management you create and have access to multi-tiered virtual environments when you develop and unit test applications. You can write your code, build and deploy the application on those environments, and run your unit tests there.

• Working with Virtual Environments for Development

Analyze Application Performance with the Performance Profiler:

• Profile client-side JScript performance in Web applications

• Focus on your own code in profiler data views and reports by using the default Just My Code filter

• Profile thread and process concurrency behavior by using new profiling modes that provide resource contention and thread interaction data for multi-processor computers and multi-threaded applications.

• Understand and change your profiling data more easily by using new graphical features in enhanced Summary views and the new Function Details views

• Understand the effect of ADO.NET function calls by including tier interaction data in your profiling sessions

• Profile on 64-bit computers and virtual servers

• Choose the .NET Framework runtime to profile in side-by-side scenarios

• Quickly isolate performance issues by using the profiler performance rules and your own custom rules

• Analyzing Application Performance by Using Profiling Tools

• Collecting Thread and Process Concurrency Data

• Concurrency Visualizer

• Summary View

• Function Details View

• How to: Collect Interaction Data for Multi-Tiered Applications

• How to: Specify the .NET Framework Runtime to Profile in Side by Side Scenarios

• Using Performance Rules to Analyze Profiling Data

Remotely Debug Message Passing Interface (MPI) Applications that are Running on a Windows HPC Cluster: You can use the MPI Cluster Debugger to simplify debugging multiple cooperating processes that are running on a remote cluster. By using the MPI Cluster Debugger, you can easily deploy required files to the cluster nodes, open the remote debugger on each cluster node, and clean up after the debugging session has ended.

• Debugging MPI Applications on an HPC Cluster

Define Your Testing Effort: You can easily define your testing effort for a specific iteration in your project and measure your progress by using a new application for testers, which is called Test and Lab Manager. You can create test plans, test suites, test configurations and test cases to define the testing required.

Visual Studio Test Elements

or

Visual Studio 2010 Ultimate

• Defining Your Testing Effort Using Test Plans

Create and Run Manual Tests: You can create manual test cases that contain individual test steps by using Test and Lab Manager. Each test step includes an action to perform and can specify an expected result. You can run these tests and mark each step as passed or failed as you perform the actions on your application under test.

You can also create shared steps that are common to multiple test cases, in order to reduce the time that is required to create test steps, in addition to the ongoing maintenance costs.

Visual Studio Test Elements

or

Visual Studio 2010 Ultimate

• Creating Manual Test Cases

• Running Manual Tests Using Test Runner

Record Manual Test Steps for Playback: You can create recordings of actions you perform for a manual test case. You can play back this recording to quickly re-run steps in a test to verify a bug has been fixed.

Visual Studio Test Elements

or

Visual Studio 2010 Ultimate

• Recording and Playing Back Manual Tests

Create Automated UI Tests: You can create automated UI tests, known as coded UI tests. You can import recorded actions and generate code that represents your UI controls, or you can locate your UI controls and perform actions on them. You can then add validation code to check that your application under test is working correctly.

Visual Studio Test Elements

or

Visual Studio 2010 Ultimate

or

Visual Studio 2010 Premium

• Testing the User Interface with Automated UI Tests

Create Physical or Virtual Test Environments To Use To Deploy Your Application or Run Your Tests: You can create physical or virtual environments that contain the set of roles that are required to run a specific application and the machines that you can use for each role.

To create physical environments you must have:

Visual Studio Test Elements

or

Visual Studio 2010 Ultimate

You must also install test agents and test agent controllers available from this additional software package:

Microsoft Visual Studio Team Agents 2010

To create virtual environments you must have:

Visual Studio Test Elements

or

Visual Studio 2010 Ultimate

You must also have:

Microsoft Visual Studio Team Lab Management 2010

For the virtual machines that you create with Microsoft Visual Studio Team Lab Management, you must install test agents and test agent controllers as required from the additional software package:

Microsoft Visual Studio Team Agents 2010

• Setting Up Test Machines to Run Tests or Collect Data

• Virtualizing the Application Lifecycle

Collect Diagnostic Data or How to Affect Your Test Machine and Easily Add Collected Data to a Bug: When you run a manual test with Test Runner, you can now make a video recording of the test case, or record the actions to a log file. You can add comments, and files such as screenshots when you run the test. In addition, for tests on applications which are in virtual environments, you can take snapshots of the environment and attach them to the bug.

1. When you run tests you can also collect diagnostic trace data (called Intellitrace data), code coverage data, or test impact analysis data. You can have your computer emulate a specific network, or you can create your own custom data diagnostic adapter.

If a test fails, you can create a bug by using Test Runner. This bug is automatically populated with the data that you collected, so that a developer can find all the information that is required to fix the bug. 

Visual Studio Test Elements

or

Visual Studio 2010 Ultimate

• Setting Up Machines and Collecting Diagnostic Information Using Test Settings

• How to: Submit a Bug using Test Runner

Group Your Automated Tests Using Test Categories: You can now group your automated tests using test categories, which are more flexible than test lists.

Visual Studio Test Elements

or

Visual Studio 2010 Ultimate

or

Visual Studio 2010 Premium

• Defining Test Categories to Group Your Tests

Increased Flexibility to Customize, Change, and Scale Out Your Build System: Whether your organization is a small startup with simple needs or a large and complex enterprise, you can design a build system topology to meet your needs today. As your code base expands and your team grows, you can quickly and easily scale your build system out one build machine (either physical or virtual) at a time.

Additional flexibility in Team Foundation Build means increased productivity for your software developers and testers. For example, build agents can be pooled and shared across an entire team project collection to ensure an efficient use of your build system hardware resources.

Pools of build agents are managed by a new entity known as a build controller. No longer does a queued build need to be stalled waiting for a single build agent to become available. The build controller delegates work to an available build agent that meets those requirements.

• Understanding a Team Foundation Build System

Easy to Create and Modify Build Definitions: You can use the Default Template to quickly define a build definition that performs the most common build tasks such as compiling code, running tests, and dropping the binaries. You can later go back and modify the build definition by using the same simple user interface.

• Define a Build Using the Default Template

Create a Custom Build Process Using Windows Workflow Designer: You can create a richly customized build process by using the Windows Workflow Designer.

• Create and Work with a Custom Build Process Template

Full Support for Legacy Build Definitions: You can use the Upgrade Template to continue using build definitions that you created by using Visual Studio Team System 2008 Team Foundation Server.

• Define a Build Using the Upgrade Template

Gated Check-in and Private Builds: Build breaks can prevent your team from making progress while you diagnose and correct the problem. You can define a gated check-in build definition to protect some or all of your codebase against build breaks. When gated check-in is enabled, changes that affect your build are automatically shelved and a build of that shelveset is queued. The changes will only be committed to version control if the build succeeds.

Your developers can also queue a private build of their code changes before trying to check them in.

• Define a Build to Validate Changes Before Check-in

• Check in Pending Changes that Are Controlled by a Gated Check-in Build

• Queue a Build

Publish data to Symbol Server: You can configure your build definition to publish symbols data to enable features such as historical debugging.

• Create and Work with a Custom Build Process Template

• For more information about Microsoft Symbol sever, see the Microsoft Web sites:

  • SymStore

  • Use the Microsoft Symbol Server to obtain debug symbol files

Enhanced Reports of Ongoing and Completed Builds: When you double-click an ongoing or completed build in Build Explorer, the system displays an easy to navigate and detailed view of data displayed in a rich UI which helps you to perform actions. For example:

• In many cases, errors are displayed as hyperlinks which you can click to view the file.

• Inside the report you can click a link or select a menu item to open the drop folder, rate the build quality, and even delete the build.

• In a graph of recently run builds of the same build definition, for each build you can view results such as, build run time and build success or failure. You can also click a bar in the graph to open the report for that completed build.

• Monitor Build Progress

• View a Build Report

Create Multi-tiered Environments for Developing and Staging Your Application: You can quickly create virtual environments that contain multiple computers for running unit tests when coding a new application or functional tests when testing it. These environments, created from clean virtual machine templates and customized to more closely match the target production environment, reduce the time that you have to spend to set up the tests and increase the time that you have available to do the testing. You can also create copies of environments without name conflicts by using network isolation.

• Working with Virtual Environments

Automatically Deploy Applications to Virtual Environments: You can use Windows workflow to automatically deploy new builds of your application to virtual computers and then run verification tests.

• Running Workflows in Virtual Environments

Use Virtual Environments in Filing and Reproducing Bugs In Your Application: Testers, you can run test cases on virtual environments, and, when you discover a difficult problem, attach snapshots of the environment to the bug. Developers, you can then connect to the snapshot of the environment where the defect was found in order to more easily reproduce the issue.

• Setting Up Test Machines to Run Tests or Collect Data

Team Foundation Administration Console: You can review the status of the servers that host the application services and configuration database, add or remove SharePoint Web applications for hosting team project portals, and manage team project collections.

• Configuring Your Server Using the Team Foundation Administration Console

• How to: Open the Team Foundation Administration Console

SharePoint Web Applications: You can use more than one SharePoint Web application for hosting the Web sites used as team project portals.

• Modify or Remove Access Between a SharePoint Web Application and Team Foundation Server

• Grant Access Between Team Foundation Server and SharePoint Web Applications

• Configure a Default Location for Team Project Portals

Project Collections: You can group projects that have similar needs or objectives, or that share common user groups, server resources, and maintenance schedule.

• Organizing Your Server with Team Project Collections

• Create a Team Project Collection

Add Servers to Existing Deployments: You can use more than one server that is running SQL Server for hosting the databases for your deployment. If you have a network load balancer (NLB) installed and configured in your deployment, you can add more application-tier servers to transparently balance the load between servers in large-scale deployments.

• Create a Team Project Collection

• For more information, see the Microsoft Web site: Installation Guide for Team Foundation.

Automatic Update of Work Item Fields that Store Person Names: You can update the name of a team member in Active Directory, and the change is automatically updated in the corresponding work item fields at the next synchronization. Automatic propagation of name changes is made to work items, work item histories, queries, and alert notifications.

• What's New in Tracking Work Items