That's just plain wrong. VB.Net is in no way, shape, or form backwards compatible with VB 6.
Try using the DEFINT command in Dot Net. Try using the Goto command. Try using the Gosub/Return commands in Dot Net. They aren't there any longer.
Dot Net may have some cool new features in it, but don't kid yourself about it being backwards compatible. It isn't. Less than 40% of VB 6 code will compile in Dot Net. The object property differences in .frms/.frxs alone is staggering...
Now, if all you've ever written are Hello World programs for your college profs, I can understand that you wouldn't comprehend that MS threw out the backwards compatibility baby with the bathwater, but if someone is paying you money for your VB knowledge, then they deserve what they've got...
If that's what you are using VB6 for, your code sucks. None of those three items have been a best practice.
I have a 25 KLOC program that converted completely, and runs without changes. The VB.NET upgrade wizard for VB6 worked perfectly. Of course, that won't be the case with all programs, but for many mainstream, conservative programs, it will be.