posts - 4237, comments - 3946, trackbacks - 370

Disclaimer

This was my personal weblog originally hosted by UgiDotNet, written mostly in Italian.

This blog is now part of my new site:
These postings are provided 'AS IS' with no warranties, and confer no rights. The views expressed on this weblog are mine alone and do not necessarily reflect the views of my employers.

Licenza Creative Commons

Tag Cloud

Archives

Post Categories

Ecco le novità di VSTS e TFS "Orcas" presenti nella CTP di Marzo...

Ecco le feature della CTP di "Orcas" relative a VSTS e TFS. In neretto le mie preferite... in rosso quelle che avrei evitato...

  • Team Architect
    • Top-down service design
      • Top-down system design allows an application architect/lead developer to perform the design of a business solution without having to be confronted with technology decisions. It enables the user to progressively refine a high-level system design, designing new sub-systems and applications in the context of the system in which they are to be used.
    • Architectural Roles on System, Applications and Endpoints
      • Enables an architect, while working on the high-level design of a system’s architecture using the System Designer, to introduce elements into the design that play a specific pre-defined architectural role(s) within architectural patterns.
  • Team Developer
    • Profiler Support for WCF Applications
      • Enable profiling of WCF based applications to improve application performance
    • Customize and extend code correctness policies
      • Code Analysis Check-in Policy improvements to communicate to a developer why the check-in policy failed and to provide guidance on how to pass the policy requirements.
    • Customize and extend code correctness policies
      • Code Analysis Check-in Policy improvements to communicate to a developer why the check-in policy failed and to provide guidance on how to pass the policy requirements.
    • Performance tune an enterprise application
      • Enables developers to run profiling during load and test procedures for a system, to see how it behaves, and use integrated tools to profile, debug and tune. This also enables performance base-lining, so that users can save a baseline profile and then, if the performance degrades, compare up-to-date traces to identify the source of the regression
  • Team Test
    • Unit Test Generation Improvements
      • Improvements to unit test generation provide an easy way for the user to specify what methods to test, and generate test methods and helper code to do unit testing, as well as providing unit test support for generics.
    • Web Test Validation Rule Improvements
      • Web Test rules improvements enable testers to create more comprehensive validation rules for the application being tested. These improvements include the following functions:
        • Stop test on error
        • Search request and response
        • Add validation rule for title
        • Redirect validation
        • Provide test level validation rules
        • Expected HTTP code
        • Warning level for errors on dependents
    • Better Web Test Data Binding
      • This feature allows users to data bind .CSV and XML files, as well as databases to a web test, using a simple databinding wizard.
    • Improved Load Test Results Management
      • With this feature user can open or remove an existing load test result from the load test repository. User can also import and export load test results files.
  • Team Foundation Server
    • Team Build
      • Support multi-threaded builds with the new MSBuild.
      • Continuous Integration – There are many components to this, including build queuing and queue management, drop management (so that users can set policies for when builds should be automatically deleted), and build triggers that allows configuration of exactly how when CI builds should be triggered, for example – every checkin, rolling build (completion of one build starts the next), etc.
      • Improved ability to specify what source, versions of source, etc to include in a build.
      • Improved ability to manage multiple build machines.
      • Simplified ability to specify what tests get run as part of a build
    • Version Control support
      • Destroy- The version control destroy operation provides administrators with the ability to remove files and folders from the version control system. The destroyed files and folders cannot be recovered once they are destroyed. Destroy allows administrators to achieve SQL server disk space usage goals without constantly needing to add more disks to the data tier machine. Destroy also facilitates removing versioned file contents that must be permanently removed from the system for any other reason.
      • Annotate - Annotate is a feature that allows developers to inspect a source code file and see at line-by-line level of detail who last changed each section of code. It brings together changeset data with difference technology to enable developers to quickly learn change history inside a source file.
      • Folder Diff - Team Foundation Server now supports compare operations on folders, whereby the contents of the folder are recursively compared to identify files that differ. Folder diff can compare local folders to local folders, local folders to server folders, and server folders to server folders. It’s a great way of identifying differences between branches, files that you’ve changed locally, and files that have changed between two points in time.
      • Get Latest on Checkout - As an optional setting on a team project or on an individual basis, you can have Team Foundation Server always download the latest version of a file when you check it out. This helps ensure that you don’t have to merge your changes with somebody else’s when you check the file back in.
    • Performance and Scale
      • This release includes numerous improvements in performance and scalability of Team Foundation Server.

Print | posted on mercoledì 28 febbraio 2007 23:51 |

Feedback

Gravatar

# re: Ecco le novità di VSTS e TFS "Orcas" presenti nella CTP di Marzo...

Perchè o lo fai di tutti i file coinvolti nelle modifiche, o ti ritrovi errori di build e inconsistenze...
Cmq... è un discorso molto lungo...
02/03/2007 13:30 | Lorenzo Barbieri
Comments have been closed on this topic.