
Originally Posted by
fafalone
Lol you're dreaming thinking there's substantial backwards compatibility in .NET.
I never made such a claim. I said the VB.Net compiler would accept just about any piece of VB6 code as valid. For example:-
Code:
Public Sub BubbleSort(numbers() As Long)
Dim i As Long, j As Long
Dim n As Long
Dim temp As Long
n = UBound(numbers) ' Get the upper bound of the array
' Main loop to control the number of passes
For i = 0 To n - 1
' Nested loop to control the number of comparisons per pass
For j = 0 To n - i - 1
' Compare adjacent elements and swap them if they are in the wrong order
If numbers(j) > numbers(j + 1) Then
temp = numbers(j)
numbers(j) = numbers(j + 1)
numbers(j + 1) = temp
End If
Next j
Next i
End Sub
You could drop the above VB6 code right into VB.Net and it would compile and work without any changes and that is no trivial thing. TwinBASIC is probably the only other compiler on the planet that would compile that with no changes. I don't expect even other BASIC variants to compile that. There is much more than just a passing resemblance between the syntax of VB6 and VB.Net.

Originally Posted by
fafalone
Superficial syntax similarities don't count for much when the entire programming model is different.
It means a LOT more than you think. Syntax is a huge part of any programming language and when moving from VB6 to VB.Net, it's one less thing you have to learn. I can personally testify that it makes the move from VB6 to VB.Net a whole lot easier.
I'm not trying to say that you're wrong, I'm just trying to put this into proper context. You will have to rewrite VB6 code from scratch if you intend on migrating it to VB.Net. You're not wrong about that but should you commit to that you will find it a whole lot less painful re-writing it in a syntax you already know. You won't be fumbling around trying to figure out how to declare an array or write a Do...While loop.