Team Development with Visual Studio Team Foundation Server

Additional Resources
• For more informational about lock types, see http://msdn2.microsoft.com/enus/library/ms181419(VS.80).aspx
What lock types does TFS support?
Team Foundation Server provides two types of locks: check-in and checkout locks. A
check-in lock is less restrictive than a checkout lock. When you apply a check-in lock,
users can continue to make local changes to the item in other workspaces. The changes
cannot be checked in until you explicitly remove the check-in lock from the workspace or
you check in the file.
A checkout lock is more restrictive than a check-in lock. When you apply a checkout lock
to a source-controlled file or folder, users can neither check out the file for editing nor
check in pre-existing pending changes. You cannot acquire a checkout lock if an item
currently has any pending changes.
Additional Resources
• For more informational about lock types, see http://msdn2.microsoft.com/enus/library/ms181419(VS.80).aspx
Distributed/Remote Development
• How do I work offline?
• How do I optimize for distributed team development?
• What is the TFS Version Control proxy?
• How do I optimize TFS Version Control proxy performance?
How do I work offline?
Team Foundation Version Control does not natively support offline working. If you want
to work offline you must strictly adhere to the following workflow:
1. Manually remove read-only flags.
2. Edit files.
3. Add or delete files.
4. Run the Team Foundation Power Tool (TFPT) online command.
Note: You must not rename any files while you are offline.
1. Manually remove read-only flags.
By default, all files in the workspace that have not been checked out are marked as readonly.
When you are working without a server connection, you must manually remove the
read-only flag from files before editing or deleting them. To do this, right-click the file in
Windows Explorer, click Properties, clear the Read-only check box, and then click OK.
Alternatively, you can use the DOS command attrib -r