To prevent errors that developers can encounter due to moving or renaming objects included in VCS, follow the 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, contact developers and inform them on the need to check in all changes.
After the check 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 an object have been moved or renamed, inform all 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 pending 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 of the folder, to which the object was moved, and check in the changes. Select the required method of conflict solving in the Resolve Conflicts dialog box. If automatic conflict solving has been selected, select the name of the file at the server in the dialog box that opens requesting the new file name.
See also: