| Reporter |
Joe White (joewhite)
|
|---|---|
| Created | Dec 16, 2011 8:22:32 PM |
| Updated | Mar 16, 2012 1:13:59 AM |
| Priority | Major |
| Type | Bug |
| Fix versions | 7.0 |
| State | Open |
| Assignee | Sergey Shkredov (serjic.shkredov) |
| Subsystem | No subsystem |
| Affected versions | 6.1 |
| Fixed in build | No Fixed in build |
If I use the "Move" refactoring to move a static method from a class to the codebehind of a Windows Form, ReSharper will correctly perform all the code changes required by the refactoring. However, it will also do a full reformat on the form's .designer.cs file (including adding "using" directives that would probably confuse the WinForms designer), despite that file having no involvement in the refactoring.
Every time I do such a move, I have to revert changes to the .designer.cs before I check in. If I had made actual changes to the form, and wanted to include them in the same commit, I would have a serious mess on my hands.
ReSharper should not modify files that were not part of the refactoring.
Every time I do such a move, I have to revert changes to the .designer.cs before I check in. If I had made actual changes to the form, and wanted to include them in the same commit, I would have a serious mess on my hands.
ReSharper should not modify files that were not part of the refactoring.