A Gathering of VS05 Team System Info

I find that in the process of learning about something, I often dig through a lot of places before I come up with what I'm looking for.

In the case of Visual Studio 2005 Team System (aka "Burton"), I wanted to know a lot more about the features that MS was building into VS for teams, including much more flexible source code control integration, web site functionality and stress testing, static code analysis like FxCop and perf. analysis built right into the build system and stats recording as part of the normal workflow for project management reporting.

In the process of gathering these details, here are the places I went:

• Official Visual Studio 2005 Team System home page
• VSTS screenshots from the MS Developer Tools Roadmap
• VSTS demonstration videos
• VSTS FAQ, including the ever favorite "Where do I get it?"
• Korby Parnell's announcement as a member of the VSTS team
• Official Visual ActiveKent Sharkey .NET SE 3.11 VSTS Announcement

Here are some things that tickled my fancy:

• Data binding to drive web site testing. I want the same thing for stand-along client testing
• The real-time stats and drill-down for ongoing web site stress testing
• Building static code analysis right into the build process so that I can fix those issues along with my compiler issues
• The idea of collecting project stats as part of what the developer is doing in VS and using those to roll-up conprehensive stats for the whole team
• Seeing our own internal tools, like PREfast, made available to our customers and integrated so nicely into VS

Some other nice places with info about it is blogs at http://blogs.msdn.com.

I remember http://blogs.msdn.com/askbarton (main blog for VSTS) and http://blogs.msdn.com/profiler (profiler blog). Also lot's of developers and testers from the team seems to have blogs now. Lot's of interesting things :)

Sounds really cool - finally a bug-tracking system integrated with a source control system!
BTW, why is MS so cautious not to use 'source control'? Has anybody seen the new source control system?

Hey Chris, are you here at Tech-Ed? Your blog post is on the Tech-Ed bloggers site, but your not in the RIO system. Hoping to get a chance to say hello in person.

Phil Haack (aka Haacked of haack.org)

LOL.. In one of the demos there is IE open with "Is Torvalds really th.." (father of linux).

So funny indeed, but I have to make a Big complain about the sound quality of the demo - it is so bad that warrants re-recording, unless you expect that no one is interested in the demos.

> Building static code analysis right into the build process so that I can fix those issues along with my compiler issues.

And here I thought you didn't see much value to test-driven development. :)

1) That's not really TDD, i.e. it's not running a set of unit tests based on planned usage.

2) What the hell are you talking about? I've been doing sorta-TDD for years and I just posted about how much I think of actual-TDD: http://www.sellsbrothers.com/spout/#Checking_Spec._Compliance_at_Build_Time