The Visual Studio Team System includes many new and enhanced features, which are summarized in this topic.
Topic Contents
Several components of Team Foundation have new features and improvements for Visual Studio Team System 2008 Team Foundation Server.
Team Foundation Build
Build Definitions
Build definitions replace the build types of Microsoft Visual Studio 2005 Team System. Unlike build types, you can use the Team Explorer user interface to modify build definitions. Build definitions also have workspace support in version control. You can now specify local paths and store the build files in any location you specify in version control. For more information, see How to: Create a Build Definition and Understanding Team Foundation Build Configuration Files.
Continuous Integration of Builds
You can specify a trigger for a build when you create a new build definition or modify an existing one. You can use on-demand builds, rolling builds, and continuous integration where each check-in starts a build. You can also define how long to wait between builds when defining rolling builds. For more information, see How to: Create a Build Definition.
Scheduled Builds
You can now run builds on a schedule, even if there are no changes. For more information, see How to: Create a Build Definition.
Build Agents
Build agents can be named independently of the build computer name. For more information, see How to: Create and Manage Build Agents. Each build agent can connect to a build computer via two ports: an interactive port and the default port used to run builds. For more information, see How to: Configure an Interactive Port for Team Foundation Build.
HTTPS and Secure Sockets Layer (SSL) for Build
You can now set up Team Foundation Build to require HTTPS and SSL. For more information, see How to: Set up a Build Agent to Require HTTPS and Secure Sockets Layer (SSL).
New Properties for Customizing Team Foundation Build
Team System 2008 Team Foundation Server includes new properties for customizing builds. These properties include customizing the behavior of C++ builds, SkipInvalidConfigurations, CustomizableOutDir, and CustomizablePublishDir. For more information, see Customizable Team Foundation Build Properties.
New Tasks and Targets for Customizing Team Foundation Build
Team Foundation Build includes a number of new targets that can be overridden to customize the build process. For more information, see Customizable Team Foundation Build Targets, BuildStep Task, GetBuildProperties Task, SetBuildProperties Task, and WorkspaceItemConverterTask Task.
Team Foundation Source Control
Destroy
You can now destroy or permanently delete source-controlled files from Team Foundation version control. For more information, see Destroy Command.
Get Latest on Check-Out
You can now enable Team Foundation version control to retrieve the latest version of a file automatically when you check it out. For more information, see Team Foundation Check-Out Settings.
Annotating Files
You can now annotate source code files. You can view line-by-line information in source code about what changes were made, who made the changes, and when the changes were made. For more information, see How to: View File Changes Using Annotate.
Comparing Folders
You can now compare two server folders, two local folders, or a server folder and a local folder using source control. You can see differences such as missing items, and items that have additions, deletions, or conflicting changes. For more information, see How to: Compare Two Folders.
Team Foundation Work Item Tracking
The performance of most work item tracking operations under a heavy load has improved significantly. When compared to Visual Studio 2005 Team Foundation Server, throughput has doubled. It now takes less time to complete individual operations. CPU usage on the Team Foundation data-tier server has been reduced. Large organizations can support more work item tracking users on their existing servers than they could with Visual Studio 2005 Team Foundation Server.
Visual Studio Team System 2008 Team Foundation Server is more scalable. Scalability has improved response times significantly of most work item tracking operations when the server is under load. This is especially true for teams of more than 500 people. Large organizations should be able to support more work item tracking users on their existing servers than they could with Visual Studio 2005 Team Foundation Server.
Team Foundation Server Management
Adding large numbers of users to Visual Studio Team System 2008 Team Foundation Server is much more reliable and less likely to cause long delays or other problems. While the total number of supported users has not changed, synchronization of users between Active Directory and Visual Studio Team System 2008 Team Foundation Server completes much more quickly.
Visual Studio Team System Architecture Edition contains new features and improvements for the following areas in Visual Studio Team System 2008:
Design Application Systems by Using a Top-Down Approach
You can now use a top-down approach to design application systems by starting with System Designer. You can start with a new system design solution or you can continue with an existing solution. You can add systems, applications, and endpoints directly to your system definition as members. You can add endpoints directly to the boundary of your system definition and delegate their behavior to members at a later time. You rename members and their underlying definitions at the same time. You can repair members of application systems that become orphaned from their definitions.
Conform .NET Web Service Endpoints to WSDL Files
You can now conform the operations in an existing .NET Web Service provider endpoint to a WSDL file.
Generate ASP.NET Web Application Projects for ASP.NET Applications
You can now select the ASP.NET Web Application template to implement an ASP.NET application. This action generates the corresponding project type for the application.
Save, Import, and Export Custom Prototypes
You can now save or install custom prototypes either for your use only or for all users on your computer. You can now install custom prototypes by importing them instead of editing the registry.
|
|
|---|
|
You still need to edit the registry to install .sdmdocument files for application prototypes created from the System Definition Model (SDM) Software Development Kit (SDK). |
You can now export custom prototypes that you want to share with others.
Select From Multiple .NET Framework Versions
You can now select .NET Framework 2.0, 3.0, or 3.5 for ASP.NET, Windows, and Office applications.
Select From Multiple Office Versions
You can now select Office 2003 or Office 2007 project templates for Office applications.
For more information, see What's New in Architecture Edition.