Move Type to Another File refactoring
This refactoring helps you move the selected type from the current file to any existing file or to a new file. If you are moving to a new file, the new file is created automatically. If there are no more types in the current file, it can be removed. All necessary imports are moved with the type. All imports that are no longer necessary are removed from the original file.
If you invoke this refactoring on a nested type, Rider will make the parent class partial, create a new file for the new part of the partial class, and move the selected type there. If necessary, you can then use the Move Type to Outer Scope refactoring to make the type non-nested and simply remove the redundant part of the parent class.
To move a type to another file
- Select a type in one of the following ways:
- In the editor, set the caret at the name of a type.
- Select a type in the Structure window.
- Do one of the following:
- Press Ctrl+R, O and then choose Move to Another File
- Press Ctrl+Shift+R and then choose Move to Another File
- Choose in the main menu.
- Type a file name in the New file name text box. You can specify the name for an existing file or a new one. In the latter case, the new file is created in the current project or folder.
- To apply the refactoring, click Next.
- If no conflicts are found, Rider performs the refactoring immediately. Otherwise, it prompts you to resolve conflicts.