I haven't done any vb.net but I can read it fairly well as I see it as the same structure as my C# coding using vba words
I like that observation as it helps explain the difference between the API's. The similarity is where the .NET API is being used. If the the ActiveX API was being used then the VB.NET code would look very close to VBA code and the C# code would look like VBA code with C# words.
The reason I suggest people moving from VBA use VB.NET is because the difference between the languages is minor. So instead of spending 4 hours learning a new Select Case they can spend it learning how to use transactions.
There seems to be a need for a place that explains the different API technologies and their benefits/disadvantages and how they are used.
Unfortunately there are people using the ActiveX API with .NET languages. In some case they have a legitimate reason. In some cases they are coming in from the outside and are ignorant of the APIs availalble. In some cases they are moving from VBA, learn the new language and continue programming just as they did with VBA so don't really gain much.
One of the arguments the C#ers have used which I think has relevance is by using C# they can make a clean break from VBA. Unfortunately I have seen ex VBAers using C# to program AutoCAD in exactly the same way as they did in VBA which has really made me cringe.
The thing I like about the .NET API users is that at the end of the day no matter what our disagreements are about languages we can see past it and help each other.