Pending Changes
Revisions to files or namespaces in Team Foundation version control are saved to your local workspace until you check in these changes. Such changes are referred to as pending changes. The Check In and Pending Changes windows are used to view and manage your pending changes.
Following are explanations of the types of pending changes you can check in.
Add
Files that you add to Team Foundation version control are treated as a pending add changes.
Edit
When you check out a file to modify in your workspace, Team Foundation makes it writable and adds an edit change to the list of pending changes for the workspace.
Rollback
You can use the tf rollback command to eliminate the impact of one or more changesets on an item. After you run the command, rollback is added to the pending changes. For more information about the rollback command, enter tf rollback /? at the Visual Studio 2010 command prompt.
Delete
When you delete a file in Team Foundation version control, it stays on the server until the delete is checked in. For more information, see Delete Files and Folders from Version Control.
Undelete
When you undelete a file, after you check in the undelete change, the file is restored from the server during the check-in process. For more information, see Undelete Command.
Rename (includes file moves)
When you rename or move a file, it is renamed or moved on the local disk, but the changes are not reflected on the server until you check in the rename change. For more information, see Move, Rename, and Delete Version-Controlled Files and Folders.
Branch
When you branch a branch, the change takes place immediately on the server; no pending change is generated. However, when you branch a folder, the branch operation is not committed until the branch change is checked in. For more information, see Branch Folders and Files.
Type
When you change the file encoding of a file, the operation is not committed until the type change is checked in. For more information, see Configure Version Control File Encoding.
The concept is flawed, in the context of all TFS check-in processes are only based upon "Pending Changes".
Many times, developers deal with files that they do not actually edit. They could be supporting DLLs, downloaded images, and then some. Bottom line, there would be no concept of "Pending Changes". But guess what, developers would still need to check them in, and keep them checked out, so others can not change them. Put another way, "Never have pending Changes". This happens a lot, but because TFS is fundamentally built around this "Pending Changes" concept, the "Check In - Keep Checked Out" concept seems to have been removed in favor of it.
The system should not think of items checked-into TFS as something that always "HAS" to ability to be changed. Old VSS had this, by simply letting poeple check items in, and keeping them checked out so other could never touch them.
TFS needs this concept removed, and made like the old VSS.
- 7/8/2011
- J-S-B
