I'm terrible sorry to talk about this argument, but I really don't understand the responses that the VB.NET Staff is giving to the community... 
Ok, now I think that eveyone know that the VB team is NOT going to be able to implement Refactoring in Visual Studio 2005. I know also that maybe the VB.NET staff is true by saying that VB.NET in Visual Studio 2005 is the best VB.NET ever, with the return of Edit and Continue features (the community request number 1), more than 500 Intellisense code snippets, My, AutoCorrect and many of other VB features.
I can understand also that implementing Refactory on VB could be a long work and a big delay on Visual Studio 2005 release date, but I'm terrible disappointed for this lack on the next VB version. Why VB must be always a step under C#? 
However, this post was only to ask a personal question: why spent so long time to implement a feature like MY?
I think I'll use it not too much often on my work and personally I don't think it could be really useful and revolutionary as someone is showing. All the things you could do in future with MY you can easily do NOW. Who has schedule the working table for the VB staff? Why the MY priority above Refactoring? Unbelievable...
We don't need toys like MY, we need working tool like Refactoring!!