Robert Green's Visual Basic Blog

VB Rocks!

What's in a name?

You probably already know this, but Visual Studio “Whidbey” is not going to be the official name of the next version of Visual Studio. Turns out it will be Visual Studio Whidbey, same name just no quotes. Isn't that funny? I just made that up. Could you tell?

Actually, the name will be Visual Studio 2005. Notice two things. First the 2005 part, indicating we won't be shipping in 2004. Also notice we are no longer going to call it Visual Studio .NET. But we will continue to call it the .NET Framework and we will continue to call them ASP.NET and ADO.NET. What about the languages? Just call them the Visual Basic language and the C# language. No .NET there. What about products. Well it would be Visual Basic 2005 Standard Edition, or Visual Basic Standard Edition version 2005. One of the two.

Does this mean .NET is dead? Of course not. We tweak names all the time. Remember when it was called Word for Windows? That distinguished it from the Word for DOS version. Eventually Word for DOS was no more and we just started calling it Word. No need to call it Office XP for Windows. Office XP only ran on Windows. And now it it officially now called Microsoft Office Word 2003. But at the end of the day it is still Word. Similarly, VB 2005 is obviously the .NET version and you know what it is, whether or not is has .NET.

Admitedly, renaming things can cause confusion. (We were asked today by our buddies at CoDe magazine about ASP.NET. They have been calling it ASP.NET “Whidbey”. What should they call it now? I have the luxury of asking the ASP team and will report back what they tell me.) But remember, we're building the next version of VS, VB, C#, ASP, ADO etc and that's what they are, regardless of what name eventually officially winds up on the box and in print. And all the new features and capabilities we have been talking about since PDC will be in there.

“What ’s in a name? That which we call a rose
By any other name would smell as sweet.”
- Shakespeare

 

Published Tuesday, March 16, 2004 12:02 PM by rgreen_msft

Comments

 

Maxim V. Karpov said:

Robert,
Well thank you for taken your time and clearifying Marketing mess. As far as developers concerned I guess most of us know the that names does not matter but our bosses the one that are making the decisions do not know, so you confuse the HELL out of them! So they think MS is not stable do you get the point?


Maxim

[www.ipattern.com do you?]
March 16, 2004 12:13 PM
 

Ian Ringrose said:

Naming is VERY important, at one place I worked at doing C++ coding, we were not allowed to update from VS6 to VS7, as the people in power did not want anything to do with .NET. (The C++ code had to also run on UNIX; therefore VS.NET was a big no-no)
March 17, 2004 7:24 AM
 

Bill Evjen's Blog said:

March 17, 2004 11:22 AM
 

Louis Parks said:

Since there is no ActiveX in ADO.NET (to my knowledge) is it fair to say you are building the next version of ADO?

ActiveX Data Objects .NET is one of the funniest IMO names I've seen for a Microsoft product.
March 17, 2004 1:26 PM
 

LeeB said:

And didn't ActiveX get re-labelled as COM so that would have given us CDO but wait, that's already collabaration data objects!

May be the IT industry are just running out of 3 letter acronoyms. I reckon there are only 17576 possible combinations (26 * 26 * 26). Using numbers as well takes us up to just over 46000 possibilities but this could cause confusion with version numbers.

I think that leaves the option of extended the alphabet or, as we've seen, start using dots!

Does anyone know if there's actually anything in the name .NET other than the obvious relationship with the Internet?
March 18, 2004 3:03 AM
 

Richard Tallent said:

I understand the need to "de-.NET" everything, I'm definitely not keen on this particular change. The term "Visual Basic" has a lot of bad baggage that shouldn't be thrust upon .NET developers and code. More:

http://www.tallent.us/CommentView.aspx?guid=3f8f528b-1981-43f4-8c1c-383f404f5aff
March 18, 2004 3:10 AM
 

Assmart said:

What about VB.NET -> VB$ (Visual Ba$ic$)

Okay that was a lot of B$
March 19, 2004 5:29 PM
 

Ken Brubaker said:

.NET stutter word is getting dropped from Visual Studio and Visual Basic
March 22, 2004 8:36 AM
 

dotbat said:

well, i got a sports car and a nice house out of knowing vb... actually more than most C++/unix gurus who are still wanking themselves raw.
June 21, 2004 1:14 PM
 

Famous Funny Movie Quotes and Stuff » Robert Green’s Visual Basic Blog : What’s in a name? said:

May 1, 2008 12:33 AM
 

Robert Green s Visual Basic Blog What s in a name | Toe Nail Fungus said:

June 9, 2009 1:50 AM
 

Robert Green s Visual Basic Blog What s in a name | work from home said:

June 16, 2009 8:40 AM
Anonymous comments are disabled

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker