TFS & my exprience

My first project after training starts with TFS integrated mode. my first experience with tfs is like a baby with first footsteps. I fell many times during the project. Since I worked on the internal project, the problem which created and solved doesnt make any harm. As developer, I developed created many projects and added to the tfs source controls.

Work in unplugged mode - TFS 2010 has a web access, which allows the user to download the source control files from browser. This allows the user to work from any place with internet enabled mode.

Here are the tips which I learned through all my experience.

1. Don't make a build error check-in - this will make problem and stops other people to work with it. Irrespective of whether the project working or not, once check-in should not affect others. To resolve this TFS 2010 came up with new feature, which checks whether the check-in has any build errors

2. Maintaining multiple workspaces - this needs a special care. If any file is checked-out in any workspace, then the file has to be checked-in or revoked by the same workspace. Atmost have 2 workspace one to work with it and another for backup and other demo purposes.

3. Adding New Item to source control - While adding new item such as projects or other documents and other PoCs, all the file has to be manually to moved to the mapping location of the source control before the project is added to the source control. Otherwise that particular project/file alone will be mapping to some different location.

Deleting a file - Deleting a item from source control is the easiest job but generally dont do that. If a file is referred by any one of the file, then don't delete the item which will make a build-error check-in.

4. Parallel & Single Checked-out - This feature allows more than one person to work on the same file. So this will lead to different branches of same file. So allowing such feature will helpful only for a small and fast development projects.

How to handle a project development in single check-out?

If the project is developed by more than one person, then project file cant be checked out by more than one person at a time. Then it will make a problem in adding new files to the project. To resolve such a situation, add just dummy/empty the files to the project and make a initial check-in without build error. Once file is added to the source control, check-out the file for edit more and work on it. This will allow other people in the project to work with it in effiecent mode.

How to hijack a file?

In the single check-out mode, if more than one person needs a same file to work with it,

then hijack the file and work with it. Say, goto the file location in explorer, then remove read only, open it in normal text editor and make the changes. This hijacked file will not be checked in and it will not take the latest as well. Such type a hijacking needs to done with more care. this will helpful in config files.

5. Shelving & unshelving - This is really a nice feature, which allows the person to put any files temporarily to the source control without making any check-in. This feature can be used in both good & bad ways :)

6. Labelling & Branching - Labelling is the feature generally used to make a source safe or to make the project to milestone. Labelling can be used to notify the development, QA and other builds. Branching is the feature used to make a same copy of the project into more than one branch. we used branching for making different versions of the project. Most important thing here is we never want to use merging unless & untill it is really needed.

7. Task & Bug - Create task & bugs of the QA, UAT in the source control and associate the check-in with one or more task & bugs. This is will allows the manager to take the project report in very easier manner. This will also allows the user to check the file & changeset history.

8. Changeset & History compare - this is the really good feature which maintains the actual development activities in a proper fashion. This is helpful in finding the right place of problems or bugs. This is also helpful for the managers to findout the right person involved in the development activity.