Microsoft has 'officially' named the Visual Studio Team System Code-name 'Rosario' suite of tools to "Visual Studio Team System 2010" in an announcement on 29-Sep-2008. They have also posted information on MSDN and Channel 9.
Here are 2 of the items that are important to me and my clients of the many announced:
- The VSTS Developer and Database Editions are being combined into a single product so you no longer have to buy Team Suite for all of your coders that also write stored procs and mantain databases. The separation of these 2 tools has been one of the barriers to bringing the database into Version Control with some of my clients. As Brian Harry puts it:
"Another key announcement is that we will be combining the Team Development product and the Team Database product into a single Team Development product (essentially giving you 2 for the price of 1). That change will be in effect go into effect on 10/1/08 (the day after tomorrow)." - Brian Harry
- VSTS 2010 allows the developer to see the state of the test system when the test failed. This was internally called "TiVo for Debuggers" which pretty much gives a nice, clear picture of what it does. Removing "Can't Reproduce" from a team's vocabulary is a big win in itself.
In Brian Harry's blog post he also stated that there would be another CTP this fall. Yippee!
Here are some links to the announcements, feature sets, goodies and articles:
Microsoft PressPass - Microsoft Unveils Next Version of Visual Studio and .NET Framework
Brian Harry's Blog - Shining the Light on Rosario
MSDN - Visual Studio Team System 2010 Overview
MSDN - Visual Studio 2010 and the .Net Framework 4.0 Overview
Channel 9 - Norm Guadagno: Announcing Visual Studio Team System 2010
Channel 9 - Visual Studio Team System 2010 Week on Channel 9!
Information Week - Microsoft Details Visual Studio 2010, .Net 4.0
CNet News - Visual Studio 2010 to come with 'black box'
RSS 3.0
1 comments:
I'm really liking the Database announcement. The previous licensing was fine for VERY large development shops - but most shops I've seen don't have "Database developers" as a unique role.
Expecting $7-10K for the Team Suite SKU per developer is pricing "Data Dude" out reach for many companies. I really thinking sticking with that would have made the Database Edition a product without widespread adoption.
Like the Work-Item-Web-Access change - it's great to see Microsoft is listening to the customers and showing flexibility on some of these licensing issues!
Post a Comment