Using local workspaces for source control

Long-time users of TFS may recall an era where using it required that their development machine have constant contact with the TFS server, even for relatively benign operations. This was because the TFS server would track the files you had on your development machine, which meant that all check-in and check-out operations required communication with the server.

The consequence of this behavior is that it makes offline work very difficult. In areas of poor network connectivity (on a plane, café, and the like), it may even mean work is prevented. Since the use of source control is something to be encouraged, this behavior is very frustrating, especially when conflicts emerge during check-ins and "get latest" ...

Get Visual Studio 2015 Cookbook - Second Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.