Placing Files under Version Control (Team Explorer Everywhere)
When you start a project, before other members of your team can access and make changes to the source code, you must share that code. You add projects to version control to enable more systematic team-based development. Each team member can check out files to make and test local changes before they share those changes with the team.
The files on your local computer (in your Eclipse workspace) are mapped to files and folders on the server by a workspace for Visual Studio Team Foundation Server. The Team Foundation Server workspace contains information about those mappings, the versions of files that are on your local computer, and any files that you have checked out.
After you add projects to version control, you can move, rename, or delete files from the server if your requirements change.
Share projects with your team: When you create a project, you add it to version control to share the project’s files with your team. You can exclude specific resources in your Eclipse project that you do not want to add to version control. You can also specify additional attributes for the Unix file system that are applied when users get a file from version control to a computer that is running Unix.
Manage files and folders on the version control server: If your requirements change, you can move, rename, or even delete files on the version control server. When other developers update their development environment, they will obtain those changes from the server.
Understand key version control concepts: When you work with files that are under version control, you work with Team Foundation Server workspaces and with changesets. You can use Team Foundation Server workspaces to manage development of multiple versions of an application at the same time. Changesets are the groups of files and related information that you check in to version control.
Get a local copy of files that are under version control: Before you start work on an application that is under version control, you must retrieve those files. You can then check out the files that you need to change. You might need to retrieve a specific version of files if you are, for example, fixing a bug in a previous version of the application.
Submit changes: When you have made and tested code changes to implement a feature or resolve a code defect, you must check those changes in to version control.
Resolving Conflicts: When you retrieve or submit files, you might receive an error that indicates that another developer has made changes to those files and that those changes conflict with your changes. You must resolve the conflicts before you can complete the operation.