Blown away by Visual Studio Team System

Attending the first Team System session…

Silos in the IT lifecycle
Infrastructure architect, business stakeholder, project manager, solution architect, developer, tester

Role-based features of VS Team System: architect, developer, tester
Integration with Microsoft Project

3 main goals of Visual Studio Team System
· Reduce complexity
· Facilitate communication
· Enable 3rd party ecosystem

Demo time. Here’s some of the stuff they showed off. They worked their way through a scenario with all the people who would be involved with a project: project manager, infrastructure architect, solution architect, developer and tester.

Enterprise source code control system. FINALLY! One scenario: Create a private branch in the source control tool – changes you’ve made can be stored on the source code repository without affecting the main source tree. They’ve made it VERY easy to put stuff into a private branch and pull it back out. Allows you to keep your source code safe without having to break the build.

There’s no built-in WinForm UI test tool. They demonstrated tight integration with a 3rd party GUI test tool though. Didn’t have to leave the Visual Studio environment to run the 3rd party tool. Results were displayed in VS environment. (The unit test and code coverage tools do come with Visual Studio Team System.)

The unit test tools allow developers to easily run unit tests. Allows the test team to dive deeper in the tests – the “easier” ones are already caught by the developer before they get to testing.

Very cool: Out of the box, the load test tool will highlight performance monitor counters that are out of “acceptable” range. You can tweak the thresholds, but the default values are threshold recommendations from MS based on best practices.

Good God! This is slick as snot!

Developers can easily add instrumentation for ASP.NET application through a wizard. The load test that the testing group is available to the developer through Team System. Dev runs the load test then can look at the result – graphic & tabular view. Easily jump to the code that might be causing performance problems from the view.

Management pack wizard allows you to easily create a Microsoft Operations Manager configuration pack. Can be included when you check in the source code. Operations folks can apply the management pack to help them monitor the production system.

Broad industry support – over 15 partners making announcements

Team System will be released in first half of 2005.

Where is a Team System build? Is it on the community tech preview? I want this NOW! I want to show this to enterprise development teams. They’re going to be blown away too. This is what enterprise developers have been asking Microsoft for for years.

YES! Most of the client tools demoed today are in the community build.

Eric Lee – demoed the developer portion of Team System

Leave a Reply

Your email address will not be published. Required fields are marked *