TFS vs Clear Case
Last week one of our customers invited us to brain storm about TFS and ClearCase. This customer has many departments; part of them work with TFS and the others with ClearCase. They want to consolidate the tools and work with only one tool.
After we asked our questions about the development process, we wrote comparison between the 2 tools.
You can read it here.
| |
TS |
ClearCase |
Comments |
| Working with VS2005 IDE |
Full integration |
Partial |
With ClearCase there is not PendingChanges window. |
| Working with another SCM tool (like VSS) |
No problem |
Problematic |
We have a scenario of: Developer has 2 projects - VS2003 project that managed in VSS, and VS2005 project managed in TFS. The developer had no problems. When we changed the VS2005 to work with ClearCase we got problems. The developer cannot work with VSS until he call the administrator and edit keys in the registry. |
| Usability / Ease of use |
Team Explorer |
Various tools |
When most of the daily operations supported by Team Explorer, the developer that works with ClearCase has a lot of applications: Project Explorer, ClearCase Explorer, Components application to create projects, VOB application for freeze projects & more. |
| Administration |
Administration can be delegated to one of the team members |
A full position administrator required |
|
| Roles and Permissions |
Every role can be delegated |
Not every role can be delegated |
In ClearCase there are roles and operations that only the administrator can execute. |
| Working with projects/solutions |
Simply from the IDE (with Team Explorer) |
Preparations required |
When you want to add new solution/project to ClearCase, first you need to open the Components and VOB applications. Note: only administrator can do it. After that you can open the IDE and work with the solution/project. |
| Working with multiple IDEs |
No problem |
Problematic |
There is a problem to open both VS2003 and VS2005 when you work with ClearCase. |