different "Encapsulate Field" dialogs

Hello Philipp,

The problem is, in code editor context menu our refactorings conflict with
Visual Studio 2005 built-in ones. So the new crappy one seems to be Visual
Studio's. We are going to give our refactorings submenu a different name
in one of future builds. For now, you can always be sure you're calling our
refactorings when you use Refactor This action or ReSharper main menu item.

Oleg Stepanov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi there

I just started with Rel. 610 on VS.NET 2005 and noticed that there are
two "Encapsulate Field" dialogs. A new one which is called directly
and the old, nice, useful, one which can be called using the
"Refactor this..." dialog.

I don't see a point in having two dialogs. Furthermore, the "new"
dialog seems to be pretty unusable (I can't even define whether I want
to have getter/setter properties). Is this work in progress or some
functionality that shouldn't really be there at all?

Cheers,
Philipp

For now, you can
always be sure you're calling our refactorings when you use Refactor
This action or ReSharper main menu item.

Or use "Refactor This" feature (CtrlShiftR).

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello Philipp,

The problem is, in code editor context menu our refactorings
conflict with Visual Studio 2005 built-in ones. So the new crappy one
seems to be Visual Studio's. We are going to give our refactorings
submenu a different name in one of future builds. For now, you can
always be sure you're calling our refactorings when you use Refactor
This action or ReSharper main menu item.

Oleg Stepanov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> Hi there
>>
>> I just started with Rel. 610 on VS.NET 2005 and noticed that there
>> are two "Encapsulate Field" dialogs. A new one which is called
>> directly and the old, nice, useful, one which can be called
>> using the "Refactor this..." dialog.
>>
>> I don't see a point in having two dialogs. Furthermore, the "new"
>> dialog seems to be pretty unusable (I can't even define whether I
>> want to have getter/setter properties). Is this work in progress or
>> some functionality that shouldn't really be there at all?
>>
>> Cheers,
>> Philipp

Hi Oleg,

That's great news! I already feared you guys were suffering from severe
fever and planning to replace the old dialog by the crappy one.

Not that I think about it, the MS dialog blends in pretty nicely with
the overall quality of the new VS2005. Hope to hear a lot of the RS-IDE
soon ;)

Cheers,
Philipp