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

New branding for Team System 2008

Jeff Beehler's Blog — Thu, 26 Jul 2007 21:56:55 GMT

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

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

MichaelGiagnocavo — Thu, 26 Jul 2007 22:03:03 GMT

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.

What's In a Name?

Doug Seven — Thu, 26 Jul 2007 22:16:36 GMT

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

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Jose Cardenas — Thu, 26 Jul 2007 22:27:00 GMT

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

Rob says: See Visual Studio 2008 Beta 2 is Served. Come and Get it!

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

davidacoder — Fri, 27 Jul 2007 00:49:27 GMT

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

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Erik — Fri, 27 Jul 2007 00:52:38 GMT

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

Etienne's VSTS World — Fri, 27 Jul 2007 01:48:49 GMT

VSTS 2008 and other news

Visual Studio 2008 Beta 2 - Downloadable now!

My VSTS Blog — Fri, 27 Jul 2007 02:15:45 GMT

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

What a week! SR1 and now Beta 2!!!!

Ponder .NET — Fri, 27 Jul 2007 04:51:57 GMT

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

University Update - Visual Basic - A Hitchhiker's Guide to Visual Studio 2008, Part I

Fri, 27 Jul 2007 09:47:35 GMT

PingBack from http://www.universityupdate.com/Technology/Visual-Basic/4144025.aspx

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Andy Mackie — Fri, 27 Jul 2007 15:12:11 GMT

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!

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Marc Brooks — Fri, 27 Jul 2007 18:44:29 GMT

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

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

Brain Matter — Sat, 28 Jul 2007 03:42:16 GMT

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

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Jeff Atwood — Sun, 29 Jul 2007 10:42:29 GMT

> Visual Studio Team Team Foundation Server 2008

Shouldn't this be..

Visual Studio Team System Foundation Server 2008?

Man, that would be nice...

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Ryan Smith — Thu, 02 Aug 2007 23:36:19 GMT

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.

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Anonymous — Mon, 06 Aug 2007 18:58:22 GMT

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.

Name translation from Visual Studio 2005 to 2008 products

Team Individualism — Fri, 10 Aug 2007 07:22:57 GMT

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

Name translation from Visual Studio 2005 to 2008 products

Noticias externas — Fri, 10 Aug 2007 07:53:53 GMT

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

MSDN Blog Postings » Name translation from Visual Studio 2005 to 2008 products

MSDN Blog Postings » Name translation from Visual Studio 2005 to 2008 products — Fri, 10 Aug 2007 08:56:10 GMT

PingBack from http://msdnrss.thecoderblogs.com/2007/08/10/name-translation-from-visual-studio-2005-to-2008-products/

VS 2008 SKUs

Daniel Moth — Fri, 10 Aug 2007 14:11:36 GMT

VS 2008 SKUs

Daniel Moth — Fri, 10 Aug 2007 14:12:19 GMT

VS 2008 SKUs

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Peter Foot — Fri, 10 Aug 2007 14:25:04 GMT

"Visual Visual Basic 2008 Express Edition"

This is a typo surely?

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Mike — Sat, 11 Aug 2007 00:44:22 GMT

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.

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

Mike — Sat, 11 Aug 2007 00:50:35 GMT

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.

Subtle changes in branding

Visual Studio Team Edition for DB Pros: The What, The Why, The How — Fri, 24 Aug 2007 21:57:56 GMT

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

Subtle changes in branding

Noticias externas — Fri, 24 Aug 2007 22:01:47 GMT

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

re: A Hitchhiker's Guide to Visual Studio 2008, Part I

jamiet — Sat, 25 Aug 2007 00:03:12 GMT

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?

[PL] Visual Studio 2008 Beta 2 - pierwsze wrażenia z pracy z narzędziem

Only Human | Devoted to technology v.2.0 — Tue, 28 Aug 2007 18:55:54 GMT

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

[PL] Visual Studio 2008 Beta 2 - pierwsze wrażenia z pracy z narzędziem

Noticias externas — Tue, 28 Aug 2007 19:06:19 GMT

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

the best online colleges in u s

the best online colleges in u s — Thu, 13 Sep 2007 10:21:53 GMT

the best online colleges in u s