When you move files and folders between projects in Visual Studio, file history is preserved. However, certain scenarios may result in unexpected behavior. Review the following considerations before moving files and folders.
Scenario: Moving a controlled file to a location where a controlled file with same name already exists.
Result: Visual Studio prompts you to overwrite this file. This replaces the file in the target location with the original file's contents. The file move is interpreted during delivery as a deletion from the source project and a modification of an existing file in the target project.
Scenario: Moving a controlled file to a location where an uncontrolled file with the same name already exists.
Result: Visual Studio prompts you to overwrite this file. Overwriting replaces the file in the target location with the original file's contents. The new file is interpreted as an addition during delivery.
Scenario: Moving a controlled folder to a location where a controlled folder with the same name already exists.
Result: Visual Studio prompts you to merge folders. Serena recommends that you do not attempt to merge folders in this way. Click No or Cancel. Because the source and target folders may contain hidden folders that contain Dimensions metadata, such a merge operation can lead to unpredictable conflicts when delivering these changes.
Scenario: Moving a controlled file to a location where a file of the same name has been deleted but not yet delivered.
Result: A warning appears and the original file will be moved to the target location. This is interpreted during delivery as a modification of the target file, and a removal from of the original file. To avoid this situation, deliver pending deletions before moving files.
Scenario: moving a controlled folder to a location where the target folder has been deleted but not yet delivered.
Result: A warning appears and the source folder is moved to the target location. During delivery, all moved content is marked as uncontrolled to minimize conflicts. Potential conflicts may result from delivering files in this scenario. To avoid conflicts, deliver all pending deletions before moving folders.
In some circumstances the file and folder information displayed after synchronization so not reflect the correct status. In such cases, close the solution and reopen it from disk.