Now granted, if you are only now getting around to writing multi-user enterprise applications (i.e. you can write everything new from scratch and have no need to leverage your existing code base), then VB.Net is OK. You don't have to throw your old applications out the window, we still have a couple of COM now COM+ apps that do mission critical work. Our most important application though was re-written from the ground up using .NET 1.0 and recently we upgraded the framework to 1.1 which caused zero issues. Our guys don't really like going back and hacking those old VB apps though, there's only about 2 guys on the entire team that keep those skills up, everyone else is apparently happy doing the .net thing. Obviously you're only going to come along kicking and screaming, but that's not the feeling I get from my development team, nor others in other organizations I interact with.
"You don't have to throw your old applications out the window, we still have a couple of COM now COM+ apps that do mission critical work. Our most important application though was re-written from the ground up using .NET 1.0..."
Oh brother. No, you don't have to throw out your old applications IF YOU DON'T UPGRADE THEM TO VB.NET! And yes, if you write your new applications from scratch, then VB.Net is fine.
But if you aren't upgrading your old applications, and if you have to move your team to a new environment for your new "from scratch" development, there are other alternatives to VB.Net (e.g. C++ and Java, among others).
What VB.Net fails to do is make a compelling case to "upgrade." That's why it has grown so much more slowly (especially compared to its full potential) than VB 6 did in original corporate acceptance.