To prevent errors that developers can encounter due to moving or renaming objects included in VCS, follow the following rules:
Before moving or renaming an object make sure that this object is not locked by other developers. Use Microsoft Visual Studio Team Explorer to check this. If there are any pending changes, you should contact developers and inform them on the need to post all changes.
After checkup an application developer may move or rename corresponding repository object. When an object is moved or renamed, the platform automatically moves or renames all server files corresponding to the object.
NOTE. When a repository object is moved or renamed, a confirmation is required to move or rename corresponding server files.
After you have moved or renamed an object, inform the application developers working on this object about it. The developers will need to refresh object navigator window, get latest version of the folder from which the object was moved and the folder to which the object was moved.
When a conflict arises related to unpublished changes in moved objects, the developer who gets the error message "TF10141: No files checked in: resolve the conflicts and try again" must solve this conflict locally. To do this, refresh repository in the object navigator, get latest version for the folder to which the object was moved, and check in the changes. Select required method of conflict solving in the Resolve Conflicts window. If automatic conflict resolution has been selected, select the name of the file on the server in the dialog box that opens requesting the new file name.
See also: