Alm Specialist Toolkit Team System Roadmap 2008 And Beyond External

Editor's Notes

• #2: Team Edition for Developers Code Metrics Code metrics is a set of software measures that provide developers better insight into the code they are developing. By taking advantage of code metrics, developers can understand which types and/or methods should be reworked or more thoroughly tested. In addition, development teams can identify potential risks, understand the current state of a project, and track progress during software development. For more information about Code Metrics, see Measuring Complexity and Maintainability of Managed Code . Profiling Tools The following features have been added to the Profiling Tools: Feature Details Windows Vista support Provides Windows Vista security compliance. IIS still requires admin rights. Allocation Stacks Collects allocation data (from the perf session property page). Available in the Allocation view performance report. Line-level sampling data On by default. Checks out the new IP and Line view performance reports (and line information in the Module view). Runtime control Starts up automatically on profiler launch. Enables and disables collection from the UI. Starts with collection disabled. Adds custom marks without editing code. Filtered analysis Filters on timestamp, process, thread, and marks. Works just like the work item tracking query system. /filterfile (saves the filter from the UI if you need the format). Diff Represents a flat diff of a single column with the ability to set a threshold for what shows up. Selects two reports in the Performance Explorer and chooses diff from the right-click shortcut menu. Chooses new diff report from the tools menu. /diff on the command line. Improved chip counter support Provides new friendlier names. Configurable xml files. PDH (Windows) counter support Filters on marks based on what the PDH data tells the user. Checks out the windows counters page of the perf session properties. /wincounter flag. Compressed report files Created from full reports. Generates small compressed files that open up very quickly. Right-click the report in the UI and choose Save Analyzed. /summaryfile on the command line. Hot Path Calltree and allocation view—shows the user the lowest performing path. Right-click on a node or use the buttons on the new toolbar. Copy to HTML Copy from the view and paste into email. cntrl-c. Load/Web test integration Creates a load or web test. Right-click and create a perf session from the test. Indigo support Profiling tools now supports Indigo. Team Foundation Several components of Team Foundation have new features and improvements for Visual Studio 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 modify build definitions using the Team Explorer user interface. You can also stop a running build and delete a completed build from the user interface. For more information, see How to: Create a Build Definition , How to: Stop an In-Progress Build , and How to: Delete a Completed Build . 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 . Build Agents   Build agents can be named independently of the build computer name. For more information, see How to: Create a Build Agent . New Properties for Customizing Team Foundation Build   Visual Studio 2008 Team Foundation Server includes new properties for customizing builds. These include customizing the behavior of C++ builds. 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 automatically retrieve the latest version of a file 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 Team Foundation Server, throughput has doubled, time to complete individual operations has been reduced, and the CPU usage on the Team Foundation data-tier server has dropped. Large organizations can support more work item tracking users on their existing servers than they could with Team Foundation Server. The scalability of Team Foundation Server has been increased so that the response times of most work item tracking operations has improved significantly 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 Team Foundation Server. Team Foundation Server Management Adding large numbers of users to Team Foundation Server is much more reliable and much 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 Team Foundation Server completes much more quickly. Architecture Edition 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 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 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. Note: You must still 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. For more information, see What's New in Architecture Edition. Team Edition for Testers Visual Studio Team System Test Edition contains new features and improvements for the following areas in Visual Studio 2008: Use unit tests in Visual Studio Professional Edition. You can now create and run unit tests in the Visual Studio Professional Edition. Run unit tests more easily. You can now run unit tests from within your code. Use inheritance between test classes. Test classes have been improved to support an inheritance hierarchy. Run unit tests on devices. You can now use unit tests to test devices. Create host adapters. You can now create a new host adapter. A host adapter lets you run tests in an environment other than the default test environment. Improved unit test data binding. You can now easily bind a unit test to a data source, including CSV files and XML files, by using a wizard. Improved Web test data binding. You can now more easily and flexibly use data binding in Web tests. Improved Web test validation rules. You can now more flexibly apply validation rules and use their results to control Web test program flow. Control load modeling. You now have more flexible ways to control the load modeling in load tests that you run. Improved load test analyzer views. New built-in graphs and viewing capabilities provide ways to more easily and quickly understand load test results. Improved load test results repository management. You can now more easily access the repository for load test results. Schematized XML file for test results. You can now programmatically work with the test results that are automatically stored in XML format in a .trx (test results) file. 06/04/09 08:55 © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.