What can you tell me about the difference

[JPnyc]

between VB and VB.net? I have experience with VB6, and also with other OOLs such as Java, but I've never touched .net at all. Any warnings, advice, pointers (did I say pointers ? ACK!), you'd care to pass on, like basic structural and syntactic differences? Thanks in advance.

[JeffMvr]

Google

[JPicasso]

.Net looks cooler on your resume.

[techgnome]

On a more serious note, .NET is much more Object Oriented than VB6. There's additions to the language, such as tha Try...Catch...Finaly block for error handling. Everything is now an object, no more using Set. Numerical alignment is now in line with other languages. What was an Integer in VB6 is now a Short, and waht used to be Long is now Int.

There's a number of changes, but nothing so Earth shattering that you couldn't pick it up fairly easily. One of the biggest changes I've seen people have problems with comes when dealing with forms. You used to be be able to create a form in the project and just use it directly. Form1.Caption ="My Caption".... now, you have to create an instance of the form before you can use it. Dim frm1 As Form1 .... frm1 = New Form1 ... frm1.Caption = 'My Caption"

TG

[pvbangera]

Check this out.

[JPnyc]

Ah, that's too bad. That's what I find annoying about other OOLs. Use objects when it's more convenient, but sometimes making a simple method that should be ubiquitous, into a whole class that must be instantiated is just a pointless pain. I suppose there's a timer class now too? Does .net require over-riding methods that you're not using like Java?

[brown monkey]

.net is java-like. you can also create static methods with regards to non-instantiating objects. like System.out.println() and console.writeline(). writeline() and println() are static methods. need not to be instantiated. it offers pure oop. overriding, overloading. blah blah. like java. though it has overrides/overloads, blah blah again. hehehe.

[mendhak]

Originally posted by DUNSEL
Ah, that's too bad. That's what I find annoying about other OOLs. Use objects when it's more convenient, but sometimes making a simple method that should be ubiquitous, into a whole class that must be instantiated is just a pointless pain. I suppose there's a timer class now too? Does .net require over-riding methods that you're not using like Java?

Look at it this way:

VB.NET is like Java in many ways, except that it pwnz Java and could use it to wipe my room's floor.