Visual Source Safe Free backup script | Simple DNS Plus Free .net API Wrapper
Team Foundation Server vs Sourcesafe
In the Microsoft Visual Studio 2005 product-line two choices are offered for software change management: Microsoft Visual SourceSafe 2005 and Microsoft Visual Studio 2005 Team Foundation Server.
Picking a solution is an important decision for any developer, whether they are working on their own or as part of an Enterprise.
Both Visual SourceSafe and Team Foundation Server are suitable for teams of all sizes, as well as individuals. There are a few key differences however between these products that make the decision relatively easy to make. The first difference is how each product is architected.
- Visual SourceSafe 2005 is a completely self-contained system that requires no other software.
- Visual Studio 2005 Team Foundation Server is a server-based system that leverages several Microsoft technologies: IIS, SharePoint Services and SQL Server 2005.
Architectural complexity is one pivot point that can be used to help decide between Visual SourceSafe and Team Foundation Server. Project complexity is another such pivot point.
- Some teams or individuals will only need source code control. Visual SourceSafe 2005 is simple, lightweight, and easy to use, and so it is ideally suited for this type of customer.
- Visual Studio 2005 Team Foundation Server supports the full spectrum of software configuration management functionality for projects that requires a detailed level of requirements management, auditing, and project management.
- The desktop-based nature of Visual SourceSafe is suitable for basic file sharing for teams who need occasional collaboration; it is not intended for scenarios where a high degree of parallel development is required.
- Team Foundation Server picks up where Visual SourceSafe 2005 leaves off in these respects. Its server-based nature is ideal for geographically distributed teams.
Visual SourceSafe is licensed individually, whereas Team Foundation Server is licensed on a server and CAL (client access license) model. For customers who will be adopting one of the Visual Studio Team System client components, using Team Foundation Server is the obvious choice, from a cost perspective.
This is a summary of 'Choosing Between Microsoft Visual Studio Team System and Microsoft Visual SourceSafe' available at MSDN, read the full article here.
Both Visual SourceSafe and Team Foundation Server are suitable for teams of all sizes, as well as individuals. There are a few key differences however between these products that make the decision relatively easy to make. The first difference is how each product is architected.
Server-Based or Desktop-Based
- Visual SourceSafe 2005 is a completely self-contained system that requires no other software.
- Visual Studio 2005 Team Foundation Server is a server-based system that leverages several Microsoft technologies: IIS, SharePoint Services and SQL Server 2005.
Architectural complexity is one pivot point that can be used to help decide between Visual SourceSafe and Team Foundation Server. Project complexity is another such pivot point.
Project Complexity
- Some teams or individuals will only need source code control. Visual SourceSafe 2005 is simple, lightweight, and easy to use, and so it is ideally suited for this type of customer.
- Visual Studio 2005 Team Foundation Server supports the full spectrum of software configuration management functionality for projects that requires a detailed level of requirements management, auditing, and project management.
Team Location and Dynamics
- The desktop-based nature of Visual SourceSafe is suitable for basic file sharing for teams who need occasional collaboration; it is not intended for scenarios where a high degree of parallel development is required.
- Team Foundation Server picks up where Visual SourceSafe 2005 leaves off in these respects. Its server-based nature is ideal for geographically distributed teams.
Cost
Visual SourceSafe is licensed individually, whereas Team Foundation Server is licensed on a server and CAL (client access license) model. For customers who will be adopting one of the Visual Studio Team System client components, using Team Foundation Server is the obvious choice, from a cost perspective.
This is a summary of 'Choosing Between Microsoft Visual Studio Team System and Microsoft Visual SourceSafe' available at MSDN, read the full article here.
» 2583 reads