Visual Studio Team Foundation Server (TFS) offers source control, data collection, reporting, and project tracking, and is intended for collaborative software development projects. It sits on a server in your organization as a project repository. It works great with the standard, professional, and Team System versions of Visual Studio. You create projects, check in code, build your projects, all because you connect to TFS. And you can customize it to work the way your team works.
But as Somasegar points out in his blog entry, Team Foundation Server – plays well with others…, TFS works well in more development environments that just Windows-centric ones.
Here are some examples of other clients can integrate.
- Eclipse projects: Teamprise is a partner-provide soltuion for working wtih non-Windows platforms including Eclipse development on Windows.
- Visual Basic 6, Visual C 6, Visual Studio 2003, PowerBuilder and others therough MSSCII client for TFS.
- Dynamics AX 2009. For a white paper, see Microsoft Dynamics AX 2009 White Paper: Team Foundation Server Version Control Setup.
On the server side:
TFS Migration & Synchronization toolkit is an open source library to build tools to sync your TFS projects with other systems or to migrate to TFS.
ClearCase Synchronization tool so you can sync your project with ClearCase.
Mercury Quality Center Synchronization is a tool that we’re currently investing in that will allow a team of testers working in QC to collaborate with a team of developers working in TFS.
For more information see, Somasegar’s blog entry on Team Foundation System.