Folks, if VB.NET programmers are "real programmers", they will, upon being presented with a menu option called Refactoring, go to Deja or elsewhere and discover what refactoring is, presuming they do not already know what it is. Andrew is a proud VB programmer, and I am darn sure he knows what Refactoring is.
But I think that the argument being discussed misses the point. In the .NET world, we're all .NET programmers. Yes, I agree that it may be a mistake (and moderately insulting) to "dumb down" the Visual Basic IDE by calling the refactoring functionality something else. But part of the problem here is that the people building the tools are still focusing on language rather than the framework. It's about the framework and the runtime, not the language, IMO. So attempting to differentiate languages by providing different IDE features for each makes little sense to me. For one thing, the more "differentiated" each language is, the more friction there is in moving from language to language. That's not a Good Thing®, IMO.
Better to provide as consistent an experience (IDE-wise) as possible in all languages, and allow developers to choose their language based on other criteria. It's not about whether I, or any other developer, VB or otherwise, know what refactoring is. It's about providing useful functionality in the IDE, and making it as simple as possible to use. So call it "Refactoring", call it "Code Cleanup", call it whatever, just make it easy to use, and make sure it's well documented. That way, whether the person using it is a newbie or an expert, a VBer or a C# whiz, they'll be able to use it to improve their code and make their lives easier. And we all want that, right?