Still using VB6 or VB.NET

[The Hobo]

Where's the option for those of us who use both?

If I make something that I'm going to send to people or distribute, I'll use VB6. But for educational purposes and dicking around, I'll use VB.Net.

So which should I vote for?

[nemaroller]

Originally posted by NoteMe
As long as the variable is 32bits long, it's faster then the original 16bit integer in VB6....

If I understand correctly, the Integer type in VB.Net could be mapped to 64bit or whatever in the future, depending on the .Net framework version. So a variable declared as Integer in v1.1 would map to 32bits, where as in v1.2, it could easily be 64bits, the framework of that future time reflecting the most optimal (native) length for the processor of the day.

The code you write doesn't change, but the underlying memory space will. Which is why most people strongly suggest using Int32 for working with the API. Then again, how long is the WinAPI going to be with us now that Longhorn is on the way. I don't have any Longhorn beta so I'm just speculating on this part.

[CornedBee]

If MS removes the API, 99% of the current applications will stop working. Sounds like a good business decision

Athlon 64 3200 (2 GHz I think)
1 GB RAM
Some Asus Mobo
Sapphire Atlantis Radeon 9800 Pro 128 MB

[NoteMe]

Then it isn't that much fater then what I have. But I still want a 64 bit prosessor.....