Feature Request

I'm going to feel really stupid if this has already been implemented,
however, I have to ask for this because I just lost around three hours worth
of work due to this.

Would it be possible to provide a different algorithm for ReSharper's
refactoring. Something to the effect of a pessimistic move.

The scenario that has plagued me (while using 1.5 and appears to continue to
plague me with 207) is such.

1. quickly prototype something
2. decide to move up/down/left/right in an attempt to create a better object
model
3. during the process of Resharper's action VS crashes (not necessarily due
to RS)
4. Upon reopening VS, notice that the code has been removed from the
original location but was not saved to the file to where it needed to go
before VS crashed

My request is something to the effect of providing for the following
sequence -

1. Move the code segment (copy, not cut)
2. Save the changes to the new location
3. Go back and "clean up" the original location

This doesn't necessarily need to be a transactional all-or-nothing, just
non-destructive move until the changes have been completed successfully.

Thanks,
Joel



2 comments
Comment actions Permalink

Hello Joel,

actually I don't quite understand how could such a problem happen, since
ReSharper (at least in 1.x)
does not save any files. When performing a refactoring, it first opens all
the affected files in the VS editor
and then modifies opened documents. So when the refactoring is completed,
you'll have a bunch of modified documents. Thus, the problem you're describing
could only occur if you accidentally
saved some (but not all) modified documents.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I'm going to feel really stupid if this has already been implemented,
however, I have to ask for this because I just lost around three hours
worth of work due to this.

Would it be possible to provide a different algorithm for ReSharper's
refactoring. Something to the effect of a pessimistic move.

The scenario that has plagued me (while using 1.5 and appears to
continue to plague me with 207) is such.

1. quickly prototype something
2. decide to move up/down/left/right in an attempt to create a better
object
model
3. during the process of Resharper's action VS crashes (not
necessarily due
to RS)
4. Upon reopening VS, notice that the code has been removed from the
original location but was not saved to the file to where it needed to
go
before VS crashed
My request is something to the effect of providing for the following
sequence -

1. Move the code segment (copy, not cut)
2. Save the changes to the new location
3. Go back and "clean up" the original location
This doesn't necessarily need to be a transactional all-or-nothing,
just non-destructive move until the changes have been completed
successfully.

Thanks,
Joel



0
Comment actions Permalink

Ahh, well . . . although this makes sense (now that you bring it up I
remember seeing this occur when Resharper did its thing), it still causes me
problems in haphazard situations - most likely due to VS. I'm sure its that
I'm expecting VS to be more stable than it truly is after moving over from 4
years of loyal use with IntelliJ.

Please, please, please bring out your IDE with local history and Perforce
integration for .Net . . . although ReSharper is a useful tool, VS is
sucking away any and all pleasure from developing in .Net

Thanks,
Joel


"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9902e88c7a441577f2445@news.intellij.net...

Hello Joel,

>

actually I don't quite understand how could such a problem happen, since
ReSharper (at least in 1.x)
does not save any files. When performing a refactoring, it first opens all
the affected files in the VS editor
and then modifies opened documents. So when the refactoring is completed,
you'll have a bunch of modified documents. Thus, the problem you're
describing could only occur if you accidentally
saved some (but not all) modified documents.

>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>> I'm going to feel really stupid if this has already been implemented,
>> however, I have to ask for this because I just lost around three hours
>> worth of work due to this.
>>
>> Would it be possible to provide a different algorithm for ReSharper's
>> refactoring. Something to the effect of a pessimistic move.
>>
>> The scenario that has plagued me (while using 1.5 and appears to
>> continue to plague me with 207) is such.
>>
>> 1. quickly prototype something
>> 2. decide to move up/down/left/right in an attempt to create a better
>> object
>> model
>> 3. during the process of Resharper's action VS crashes (not
>> necessarily due
>> to RS)
>> 4. Upon reopening VS, notice that the code has been removed from the
>> original location but was not saved to the file to where it needed to
>> go
>> before VS crashed
>> My request is something to the effect of providing for the following
>> sequence -
>>
>> 1. Move the code segment (copy, not cut)
>> 2. Save the changes to the new location
>> 3. Go back and "clean up" the original location
>> This doesn't necessarily need to be a transactional all-or-nothing,
>> just non-destructive move until the changes have been completed
>> successfully.
>>
>> Thanks,
>> Joel
>



0

Please sign in to leave a comment.