2 ms·
Why not looking into VB.net? I mean I know that Microsoft is trying to kill it so not sure it is a long term solution, though I would expect long term support e
by cm2187 4y ago
Why not looking into VB.net? I mean I know that Microsoft is trying to kill it so not sure it is a long term solution, though I would expect long term support even if you don’t get new features.
If you are familiar with VB6 there is not a lot of difference. Set keyword removed. All collection zero based instead of inconsistent 0 and 1 based. A null and empty string are two different things. Parameters are byval by default instead of byref by default. And you get lots of nice features: generic, linq, return keyword, try/catch, etc. Otherwise the syntax is the same, and winform also works in a very similar way.
I did the transition VB6 => VB.net => C# (the latter when VB got deprecated).