"As I already said, it depends on what you're using it for. If your building large multi-user enterprise applications, .NET is far superior."
No, VB.Net has an inferior error detection and correction architecture that requires the programmer to code every line she desires to check for an error by hand, rather than the old VB 6 way of identifying a single error handler and turning on automatic error detection that checked at every line for you. VB.Net is also inferior with VBA application integrations (typically the most used applications in many firms, e.g. MS Word, MS Excel).
But worse, VB.Net can't handle *existing* VB 6 multi-user enterprise applications. So your existing multi-user enterprise applications are screwed if you want to upgrade to VB.Net.
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.
Not great. Just OK.
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.