Classic?
I thought VB6 was still alive. :cry:
Printable View
Classic?
I thought VB6 was still alive. :cry:
There's always one isn't there :afrog:
We need to differentiate more between .NET and VB5/6...
Fair enough, good differentiation. :afrog: :D
Can't you write
Classic Visual Basic X
or
Visual Basic X
or
Visual BAsic 1-6
or
Visual Basic 4/5/6
or something...
General Visual Basic (Not .NET, the other ones. You know, 1 - 6. The ones before .NET came out. Yeah them.)
I was always partial to "Visul Basics"
:p
Need to be careful, because the next version of Visual Basic most likely won't have ".NET" in its name.....
Visual Studio 2005 is the announced name for Visual Studio -- note there is no .NET. :)
Brad!
Why can't we simply call it Visual Basic 1-6 ???
Yeah what about: Visual BASIC (Pre .Net)
Like you have in the comment for it.
Mind I don't actually mind Classic Visual BASIC.
I'm willing to consider additional changes.
Get agreement with forum's moderators on what to change it to and then I'll look at changing it.
Brad!
How about "Visual Basic (Episodes 1 - 6)" or "Visual Basic (Seasons 1 - 6)" or "Visual Basic (I - VI)" or "Visual Basic (not .NET)" or "Visual Basic (.NET - NOT!)"
TG
:bigyello:
Visual Basic 4/5/6
Would be better with the search engines, more noticeable than "Classic Visual Basic"
Remember, search engines are important.
ahem
SOME of us are still desperately clinging to "classic" vb
it's still hip, it's still with it
With this in mind and known Micro$oft - VB.Net may become the "classic" as soon as next year. :bigyello:Quote:
Originally posted by brad jones
... Visual Studio 2005 is the announced name for Visual Studio -- note there is no .NET. :)
Brad!
Visual Basic Classic makes it sound like a soda. Mmmm.... I lke Coke. (and it's the first thing I thought of when I saw the new title to the section.)
Wouldn't it be better if you could make me think of Pepsi insead?
Quote:
Originally posted by qbaholic
Wouldn't it be better if you could make me think of Pepsi insead?
Visual - It's the Basic.
Yeah, go with Visual Basic 4-6 (screw the ones before 'em). And why are we worrying about something thats not going to be released until next year? :confused:
I will go for: Visual Basic 4-6
Too. :D.
Personally, I prefer the Visual Basic X, but why not just Visual Basic. If both are present, (VB.NET and Visual Basic) People will know the difference.
But they don't! I can't tell you how many times I move posts from new people from VB to .NET.Quote:
Originally posted by qbaholic
Personally, I prefer the Visual Basic X, but why not just Visual Basic. If both are present, (VB.NET and Visual Basic) People will know the difference.
I can't tell you how many times I've noticed you move them!Quote:
Originally posted by MartinLiss
I can't tell you how many times I move posts from new people from VB to .NET.
We can't ignore'm all - there are many busineses that still using VB3 which was pretty much major release at the time.Quote:
Originally posted by Pc_Madness
Yeah, go with Visual Basic 4-6 (screw the ones before 'em)...
I think Visual Basic: Old School would work best. :)
I think that standardization of name is a good thing. Don't you think that you might confust the new users to this forum by using two names for the same thing. One or the other should change to match the other so that there is no confusion then.
"CodeBank - Visual Basic 6 (and before)"
"Classic Visual Basic"
Hmm.... maybe the "Classic Visual Basic" should be changed to "Visual Basic 6 (and before)"
How important is nomiclature anyway?
Visual Basic.NET and Visual Basic.NOT
:confused:Quote:
Originally posted by Slaine
Visual Basic.NET and Visual Basic.SNOT
Visual Basic 3/4/5/6 then. :p
Since its been explained VB.Net is a one shot Name, we could have the following:
VB.BeforeNet
VB.Net
VB.AfterNet
:wave:
Quote:
Originally posted by Slaine
Visual Basic.NET and Visual Basic.NOT
:D :D :D :D :D