Communicate with Your Teammates When Locking Files

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

If you do lock a source file, let your teammates know so that they can plan their work around the unavailability of the file. Explain why you need an exclusive lock on the file and how long you are likely to retain the lock. By locking a file, you potentially introduce a bottleneck into your development cycle, if other developers need to work on the same source file.

Only lock a file while editing it if you are concerned that there will be a conflict resulting in a complicated manual merge operation. Where possible, prefer shared checkouts by selecting the lock type None when you check out the file.

To lock a file from Source Control Explorer, right-click the file, click Lock, and then select the Check Out or Check In lock type.

Additional Resources

Last edited Jul 26, 2007 at 9:54 AM by prashantbansode, version 3


No comments yet.