My biased view says to learn C#, and eschew VB.NET.

This way, you get less illiterate replies asking you for thousands of lines
of code to do something you've vaguely suggested you can do, when you post
about your current coding explorations. :)

And less people mistaking you for a VB6 or VBA guru, because you put V and B
next to each other in a post. :)


My unbiased view also says to learn C#, for much the reason given above...
VB.NET code will keep dragging you back to your VBA mindset, or at least
towards it.

Reply via email to