My experience all suggests that pure-VB (even .NET) is a treacherous dead-end, because it doesn't scale in terms of complexity and project size, and the point at which is stops scaling is often unrealized by its developers.
- VB(.NET) is amazing for small, simple gadgets.
- VB(.NET) is terrible for large or complex systems.
The problem is that VB is likely to be the only programming language that developer knows (moreso than developers in other languages).
Consequently, when they reach the end of the reasonable VB road... they will NOT say "Oh, I should learn C#."
They will say "How can I make this work in VB?"
And that's when you start to get business-ending unsupportable messes of spaghetti code that just barely work, on a good day.
Give a person only a hammer, and they'll find a way to make the entire world a nail.