I thought they weren't going to call it "Refactor" because it might confuse some developers. I hope you can talk them out of changing it to something "less confusing".

Interesting. Finally they know VB team screm up big time. Why they cannot ask C# team to finish the job, so that the whole thing is consistent?

Kai - you kidding man? They're probably too busy trying to figure out how to implement background compilation in C#, let alone release a decent version of a refactor tool. From what I've seen, DevExpress's edition is waaaayy better than what's in C#. Everything in C# seems to be half-baked so it's not too "easy" to use. God forbid it makes us feel dumb, like the VB duh-velopers who are busy getting apps out the door. Get real man...

It does look amazingly cool! The one big disadvantage it will have over the c# refactor tool will be that it probably will not integrate with the class designer. The recent Channel 9 video on the class designer made it quite clear that to get it finished fo release, it would not be extensible.

Tim: Just an FYI, it is my intention to integrate Refactor in every way that makes sense and feels right, and the class designer is definitely one of those areas we're looking into. It's both a priority and a challenge, which means I can't guarantee that we'll deliver it, but I can guarantee that we're looking into a safe way to integrate here.

Refactor is built on the free DXCore visual extensibility engine (http://www.devexpress.com/DXCore), which can already do things that VSIP and the normal VS Extensibility model can't do (like painting on the editor), so just because MS says something isn't extensible doesn't necessarily mean that it's impossible.

Does C# have the option to use the "Developer Express refactoring" tool? Or "Developer Express refactoring" is VB only?

Its def cool that there including it but it has a tendency to crash VS2005 beta2 at the moment - hopefully they'll fix it as they integerate it into the RTM or a later CTP.