Visual Basic 9

[agmorgan]

This was linked to from the VBWire ads
http://www.computerworld.com.au/inde...7;fp;16;fpid;0

What happened to Visual Basic 8???

[dglienna]

Maybe "Orcas" is v8?

The .Net Language Integrated Query Framework, which is planned for the future "Orcas" release of the Visual Studio toolset,

It's due in November for Longhorn/Vista

[RobDog888]

VS 2003 was 7.0 and isnt VB 8.0 VB 2005? So VS 9.0 would be the next version after 2005.

[Hack]

VS 2003 was 7.0 and isnt VB 8.0 VB 2005? So VS 9.0 would be the next version after 2005.

You beat me to it, but this is the way I understand the versioning to be.

[techgnome]

So what about VS2000? Wouldn't that have actualy have been 7.0?

Tg

[NoteMe]

Techgnome is right..there was something weird there...but I also seem to recall that there was something called 7.1 compiler. Becasuse VS was not fully .NET in 2000, so they fullfilled the rest of the .NET parts in 03. But to be honest. The numbers are totaly out of controll now. Brad Jones wrote in one of his articles about C# 3.0, but version 2.0 is not out yet. But he talked about Generics something that will be implemented in 2.0, so I think it is more then we that are lost with the numbers right now.. They should do as DX...

Summer 2004
October 2004
Feburary 2005
April 2005

Much easier to figgure out..



- ØØ -

[Hack]

So what about VS2000? Wouldn't that have actualy have been 7.0?

Tg

If memory serves, VS 2000 did start out as VS7 (just like Windows 2000 started out as NT5), but got changed before it was ever released.

[NoteMe]

Ehhh brain fart....what did you actualy mean Techgnome....I think I must have had a brain fart...

Was there a VS 2000 version? Or did you mean VS 2002?

At least here is the list.

VS 6 - 6.0 compiler
VS 2002 .NET - 7.0 compiler
VS 2003 .NET - 7.1 compiler
VS 2005 .NET - 8.0 compiler

- ØØ -

[Hack]

I distinctly remember the NT5/Windows 2000 thing because at the time I was doing a job with a team from Microsoft Consulting, and purposely kept referring to their new, and at that time, unreleased, new OS as NT5. This really used to tick them off.

I do remember talk of VS 2000, but I don't believe it ever got released. I think NoteMe is right about the first actual product to hit the market place being 2002.

[RobDog888]

Yes Hack, it went like this...

VS 98 (6.0.8988)
VS 2002 (7.0)
VS 2003 (7.1.3088)
VS 2005 (8.0) ?
VS 200? (9.0) ?

[NoteMe]

Yes Hack, it went like this...

VS 98 (6.0.8988)
VS 2002 (7.0)
VS 2003 (7.1.3088)
VS 2005 (8.0) ?
VS 200? (9.0) ?

You can't say that VS2003 had compiler version exactly 7.1.3088.. It started as 7.1, then there came additional processor packs. Like the addition of SSE instruction sets and so on.....thats why the number grew. And I guess the same has happend to all the other compiler versions too, and it looks like it has all ready started to the version 8 compiler too...

- ØØ -

[RobDog888]

Well who wants to run VB6 without the service pack 5 installed? So your saying that you are running 6.0 without any SPs? For most people there will be a difference because most dont get it leagally so they cant contact MS for the Updates. So they will be running 7.1.0000, etc

[NoteMe]

Don't mix SP and Processor packs...


- ØØ -

[RobDog888]

Why is it like a "Dont mix acids and bases" type of thing in chemistry? jk. No, your right.

[Phill64]

It seems 2005 is VB8.0 as you say, i looked around and found code examples for VB8.0 beta 2

but what happend to the other languages, does that mean C# is already C# 2.0 ? why are the versions going up so quickly lately? we're already talking about C# 3.0 and VB9.0 it's getting pretty ridiculous, it's going to be even harder for everyone to make code samples, by the time samples are written the new version is out, do you think this will keep going like this or they'll reach a point where they will stop for awhile? like maybe VB10 and C# 4?

[RobDog888]

They are now talking about VB18 and C#12 ! By the time we are able to get the new version they are already a couple of version ahead and developing. Why dont they just say, "Hey this is an update" and not force us to learn new coding logic and syntaxes. They need to give us some time to get up to speed on the newly released version before they start with 3 versions ahead!

[Phill64]

They are now talking about VB18 and C#12 ! By the time we are able to get the new version they are already a couple of version ahead and developing. Why dont they just say, "Hey this is an update" and not force us to learn new coding logic and syntaxes. They need to give us some time to get up to speed on the newly released version before they start with 3 versions ahead!

that's insane! what the hell are microsoft doing? are they developing these things like games? team1 make VB9 team2 make VB10 team3 make VB11 hut hut go! go go!

I don't think they are doing themselves any favours by doing this, they may earn some money from more sales but i think it will hurt their name and stop the sales, if it's too difficult to be an MS language developer because every 6months the objects and classes you use become obsolete

[RobDog888]

You do know I was kidding about VB18 and C#12? Just feeling like you, tired of playing catch up all the time. Cant even get guru experience and then they come out with another completely different version.

[Phill64]

You do know I was kidding about VB18 and C#12? Just feeling like you, tired of playing catch up all the time. Cant even get guru experience and then they come out with another completely different version.

i had just a little hunch 18 and 12 were exagerated yes

but it's true that they come out making announcements of versions a level above what they currently havnt released, i mean isnt 2005 even still a beta? which i havnt yet got and feeling behind

i feel sorry for the guys still using vb6, by the time they get around to jumping onboard .net they will be going from vb6 -> vb10 and have no idea what theyre doing

what about C# that's something i still havnt got into using yet, i've used the c++ stuff in VS, but not C# do the versions effect it too much?

[RobDog888]

Not sure since I havent learned C# yet but I would have to imagine that t would get affected by framework changes as much as vb does plus any other syntax and logic changes to the code.

[NoteMe]

What do you mean by "version effecting it too much"? C# is a sweeeet language....just look at DoomSharp... And the syntax is not changed between '05 -> '05 (something I doubt they will do in VB too), but they are adding stuff. Adding generics and a lot of other stuff I used to use in C++, but havn't been able to do before now in C#. It is sweet sweet.


Just as a comment to this:

i feel sorry for the guys still using vb6, by the time they get around to jumping onboard .net they will be going from vb6 -> vb10 and have no idea what theyre doing

VB6 programmers didn't know what they where doing when they moved or did not move from 6->7 either...that was where the changes was...


- ØØ -