When you download and install Visual Studio 2008 Beta 2, you may notice that some of the product names have changed for this release. On the Help menu in Team Suite, click About and you'll find that many of the products in Team System have a new name.
Since we released Visual Studio 2005, we’ve heard from you that the capabilities of each of the team editions don’t always map to the way you define roles in your organizations. To simplify the naming and respond to this feedback, we’ve renamed the team editions to remove specific role names. Of course, this doesn’t mean we’re changing Team System’s charter – it’s still designed to help everyone on the team collaborate together through integrated tools, processes, and guidance.
Below is a list of the name changes compared to what they were in Visual Studio 2005.
However, the names for the rest of the Visual Studio product line are unchanged except for the version change.
Check out Rob's blog announcing the new branding for Team System 2008 . In it, he writes: Since we released
I still wish the individual SKUs would be destroyed and then we'd have Visual Studio 2008 Professional and Team. I have yet to see how disabling certain features actually works on smaller teams -- everyone ends up getting Team Suite anyways, at the cost of lots of confusion about the lesser versions.
My colleague, Rob Caron , just posted the latest news on upcoming name changes for some of the Visual
And where can we find the link to download vs2008 beta 2?
"we’ve heard from you that the capabilities of each of the team editions don’t always map to the way you define roles in your organizations"
And as a response you change the names?!? The NAMES aren't the problem...
I don't see how renaming them changes the fundamental problem. Do developers not need to test? Are database devs not interested in architecture (or testing?)
Unless you have a big, highly silo'd team, you have to buy team suite anyway. Or you just buy the Dev version and do without data dude and use nunit and test driven or resharper for testing. The architect suff isn't fully baked in 2005. It might be better in 2008 and worth paying for.
You need to think about horizontal integration and creating horizontal layers - which has always been the successful pattern for MSDN - rather than vertical silos.
VSTS 2008 and other news
Well the blogosphere's already running hot ( Soma , Rob , Scott to name a few) with the news that Visual
VS 2008 here I come!!!!! First the Database Professionals team gets SR1 out the door. Now DevDiv at Microsoft
PingBack from http://www.universityupdate.com/Technology/Visual-Basic/4144025.aspx
Due to the high cost of Team Suite, my experience is people just choose Developer, and miss out on all the other functionality.
Do the VS sales figures bear this out ?
I agree with suggestions that individual SKUs should be destroyed, and just have Visual Studio 2008 Professional and Team - provided the pricing is similar to Developer, not the price of suite!
It's not the NAMEs that need changing, it's this ridiculous fragmentation into too many different SKUs that needs to end!
Why not drop the word System from the Team SKUs. It's pretty darn meaningless.
Visual Studio 2008 Beta 2, Silverlight, Rosario, and more!
> Visual Studio Team Team Foundation Server 2008
Shouldn't this be..
Visual Studio Team System Foundation Server 2008?
Man, that would be nice...
While I appreciate renaming the products to better describe their role....I think the whole package needs to be re-evaluated. Too many sku's too much confusion. Visual Studio 2008 Profession and Team would be fine....I still don't know what the difference is between Visual Studio Team System 2008 and Visual Studio Team System 2008 Team Foundation Server and does Visual Studio Team System 2008 Team Suite contain everything?
Like someone said earlier in a small team you have to buy the whole suite anyway...I'm sure not too many people bought Architect and Database but skipped Developer.