| Reporter |
Alexander Groß (alexandergross)
|
|---|---|
| Created | Dec 13, 2011 3:49:04 AM |
| Updated | Dec 14, 2011 9:54:55 PM |
| Priority | Major |
| Type | Usability Problem |
| Fix versions | Mirabile Futurum |
| State | Open |
| Assignee | Sergey Shkredov (serjic.shkredov) |
| Subsystem | Refactoring |
| Affected versions | 6.1 |
| Fixed in build | No Fixed in build |
Consider the following VS solution:
The end result is this:
The end result is this:
In Scenario B the folder disappears and I don't see why that is useful. With files in subfolders of the "folder" the whole structure is actually flattened. I was under the impression "Put classes into separate files" can be subsumed as "Refactor | Move types into matching files".
- project-a\folder\file.cs
- project-b which is empty
Scenario A
- Right-click the "folder" folder and select Refactor | Move...
- In the dialog, choose "project-b" as the target
- Select "Preserve hierarchy of folders and file names"
- Complete the refactoring
The end result is this:
- project-a which is empty
- project-b\folder\file.cs
Scenario B
- Right-click the "folder" folder and select Refactor | Move...
- In the dialog, choose "project-b" as the target
- Select "Put classes into separate files"
- Complete the refactoring
The end result is this:
- project-a which is empty
- project-b\file.cs
In Scenario B the folder disappears and I don't see why that is useful. With files in subfolders of the "folder" the whole structure is actually flattened. I was under the impression "Put classes into separate files" can be subsumed as "Refactor | Move types into matching files".