<P> TFVC is a centralized version control system allowing teams to store any type of artifact within its repository . TFVC supports two different types of workspaces when working with client tools - Server Workspaces and Local Workspaces . Server workspaces allow developers to lock files for check - out and provide notification to other developers that files are being edited . A frequent complaint for this model is that files on the development machine are marked as read - only . It also requires developers to "go offline" when the server can't be contacted . Local workspaces were designed to avoid these problems . In a local workspace scenario files are not read - only and they do not have to be checked out before working on them . As long as the files are on the developer's local machine, it doesn't matter if the server is connected or not . Conflicts are dealt with at check - in time . </P> <P> To improve performance for remote clients, TFS includes the ability to install Proxy Servers . Proxy servers allow source control contents to be cached at a site closer to the developers to avoid long network trips and the associated latency . Check - ins are still performed directly against the TFS application tier so the Proxy Server is most beneficial in read scenarios . </P> <P> As part of the source control engine, TFS supports a number of features to help developers ensure the code that is checked in follows configurable rules . This rule engine is called a Check - in Policy . There are several out of the box policies such as the Changeset Comments Policy which will not allow a check - in unless the developer enters a check - in comment . These policies are extensible and can be used to examine all aspects of the code being checked in, the comments and the related work items . TFS also supports a Code Analysis feature that when used independently is known as FxCop . The inclusion in TFS means that the analysis can run against code checked into the server and during automated builds . </P> <P> With the release of TFS 2013, Microsoft added native support for Git . This is not a Microsoft specific implementation but a standard implementation based on the libgit2 library . This is the same library that powers the popular GitHub and the code is freely available from GitHub . Because Microsoft took the approach of using a standard library, any Git client can now be used natively with TFS (in other words, developers can use their favorite tools and never install the standard TFS clients). This allows tools on any platform and any IDE that support Git to connect to TFS . For example, both Xcode and Android Studio support Git plug - ins . In addition, if developers do not want to use Microsoft's Team Explorer Everywhere plug - in for Eclipse, they can choose to use eGit to connect to TFS . </P>

One of the features of tfs is version control