I'm not sure how I feel about the "new cool movement" to stop using Hungarian notation in VB.NET. Here's quick quote from usenet:

The unbridled use of Hungarian notation has the immediate consequence that it becomes terribly easy to fail to attach meaningful names which clearly describe a variable. In Code Complete, Steve McConnell notes that Hungarian notation 'encourages lazy, uninformative variable names'. Hungarian notation as it stands is simply useless; it is too much an invitation to make a mess of one's program. One can regard and appreciate the examples given as enough to end its use.

I've actually used Hungarian in my Java code fairly often, substituting VB6 prefixes where the objects most closely match, though I also tend to use a lot of Smack smack = new Smack(), with the var the same name, different first letter case, as its type (which doesn't work in VB.NET -- or does it? Seems to let me get away with it). With IDEs with autocomplete, it's a big help, and also helps you quickly view what sorts of child objects something you're messing with has. It's a useful commenting scheme, and those that say, like the previous post that I linked to, that comments lie and shouldn't be used are just plain silly. Sure, there's no machine readable link between comments and code, but that's no excuse to be lazy. Let's assume the IDE wouldn't build your app if comments were out of sync -- a good coder will go through the same amount of work with or without the extra check.

I do, however, know how I feel about this quote, later on in that post:

Am I to judge Charles Simonyi for having created of this monstrosity? Surely he meant only the best, and could not have foreseen the damage to young, impressionable programmers that would subsequently result from it. When he joined Microsoft back in 1981, he brought this notation system from his work in the 1970s at Berkeley and Xerox Palo with him, who subsequently spread it by force to the entire planet.

"As if code rusted."