A Hitchhiker’s Guide to Visual Studio 2008, Part I


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.


 






























Visual Studio 2005 Visual Studio 2008
Visual Studio Team System Visual Studio Team System 2008
Visual Studio 2005 Team Suite Visual Studio Team System 2008 Team Suite
Visual Studio 2005 Team Edition for Software Architects Visual Studio Team System 2008 Architecture Edition
Visual Studio 2005 Team Edition for Software Developers Visual Studio Team System 2008 Development Edition
Visual Studio 2005 Team Edition for Software Testers Visual Studio Team System 2008 Test Edition
Visual Studio 2005 Team Edition for Database Professionals Visual Studio Team System 2008 Database Edition
Visual Studio 2005 Team Foundation Server Visual Studio Team System 2008 Team Foundation Server
Visual Studio 2005 Team Test Load Agent Visual Studio Team System 2008 Test Load Agent

 


However, the names for the rest of the Visual Studio product line are unchanged except for the version change.


 
























Visual Studio 2005 Visual Studio 2008
Visual C# 2005 Express Edition Visual C# 2008 Express Edition
Visual C++ 2005 Express Edition Visual C++ 2008 Express Edition
Visual Basic 2005 Express Edition Visual Basic 2008 Express Edition
Visual Web Developer 2005 Express Edition Visual Web Developer 2008 Express Edition
Visual Studio 2005 Standard Edition Visual Studio 2008 Standard Edition
Visual Studio 2005 Professional Edition Visual Studio 2008 Professional Edition

1321

Comments (30)

  1. Check out Rob’s blog announcing the new branding for Team System 2008 . In it, he writes: Since we released

  2. MichaelGiagnocavo says:

    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.

  3. Doug Seven says:

    My colleague, Rob Caron , just posted the latest news on upcoming name changes for some of the Visual

  4. And where can we find the link to download vs2008 beta 2?

  5. davidacoder says:

    "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…

  6. Erik says:

    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.

  7. VSTS 2008 and other news

  8. My VSTS Blog says:

    Well the blogosphere’s already running hot ( Soma , Rob , Scott to name a few) with the news that Visual

  9. Ponder .NET says:

    VS 2008 here I come!!!!! First the Database Professionals team gets SR1 out the door. Now DevDiv at Microsoft

  10. Andy Mackie says:

    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!

  11. Marc Brooks says:

    Why not drop the word System from the Team SKUs.  It’s pretty darn meaningless.

  12. Brain Matter says:

    Visual Studio 2008 Beta 2, Silverlight, Rosario, and more!

  13. Jeff Atwood says:

    > Visual Studio Team Team Foundation Server 2008

    Shouldn’t this be..

    Visual Studio Team System Foundation Server 2008?

    Man, that would be nice…

  14. Ryan Smith says:

    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.

  15. Anonymous says:

    The VS marketing team should be embarrassed by this.  This overwhelmingly and unnecessarily confusing and complex, and just serves to reinforce all of the negative stereotypes about Microsoft.

    The real question is – what problem is this trying to solve (or rather, what problem is this actually solving?)  Are the feature differences in each of these 14 SKUs so diverse and so attuned to specific developer roles that they justify the sheer ridiculousness of their existence? Additionally, did it occur to anyone that names like "Visual Studio Team System 2008 Team Suite" are just absurd?  

    I feel just as bad for the Microsoft sales folks as I do for the developers who have to endure this.  Discussion of the naming alone must completely undercut the value discussion.

  16. According to Rob Caron recently : Visual Studio 2005 Visual Studio 2008 Visual Studio 2005 Team System

  17. According to Rob Caron recently : Visual Studio 2005 Visual Studio 2008 Visual Studio 2005 Team System

  18. Peter Foot says:

    "Visual Visual Basic 2008 Express Edition"

    This is a typo surely?

  19. Mike says:

    My opinion is that there should be 1 (ONE) Visual Studio. You’d use profiles to create different layouts and load different parts. So database admin profile is very different from web developer profile.

    The simplicity of 1 program for developing on Windows is just very appealing. Make it $699 and you’re set. In fact, I have no idea why you want to make so much money on the IDE, but I think free as in beer would be too much to ask.

  20. Mike says:

    In fact, not only should Microsoft drop the many versions of Visual Studio, they should also combine all the Express versions into one Express version (currently it makes no sense).

    Visual Studio 2008 Express

    Visual Studio 2008 Professional

    Visual Studio 2008 Team

    Doesn’t that simplicity appeal to you? Probably deep inside it does, but the marketing guys just love their product differentiation.

  21. I wanted to point out a post that Rob Caron put out a few weeks back that is worth mentioning, as it

  22. I wanted to point out a post that Rob Caron put out a few weeks back that is worth mentioning, as it

  23. jamiet says:

    Rob,

    Apologies for my naivety but could you point out the difference between “Visual Studio Team System 2008” and “Visual Studio Team System 2008 Team Suite”? I’m still confused by the whole Team Suite thing (great products though they are).

    You are hereby added to my feed reader so I’ll hope for a reply soon :)

    -Jamie

    Visual Studio Team System 2008 Team Suite is a product SKU that encapsulates of all of the team editions (Architect, Database, Development, and Test). Visual Studio Team System 2008 is the name of a product family that includes the above, plus Team Foundation Server and Test Load Agent. Visual Studio Team System 2008 is like the Microsoft Office 2007 system. You can’t buy it, but you can buy the products that are a part of it. Does that help?
  24. Urlop się pokończył, znalazłem w końcu trochę czasu aby się pobawić nową betą VS.NET 2008 , która została

  25. Urlop się pokończył, znalazłem w końcu trochę czasu aby się pobawić nową betą VS.NET 2008 , która została