I reported earlier that one of the refactorings in the new Visual Studio 2005 beta broke the functionality of the application by using a name that caused shadowing of another variable.

I got a response from Microsoft on this issue. Here's their answer:

Thanks for reporting this issue. Verification is built into most of our most commonly used refactorings (such as rename), but is unfortunately not built into all of our refactorings as of date. This was one of those hard decisions where we needed to make a tough call between the benefit of adding another refactoring and the cost of fully building in a verification stage with it. We decided that in this case, there was a greater benefit to add the refactoring, but we will definitely be looking at adding verification in a future version.

So they'd rather release a refactoring knowing that it can break code than to spend the time to fix it. It's their call to make. Just don't expect me to have confidence in their refactorings.