05 May 2008

Are you still using Visual SourceSafe !!! ?

According to the Visual SourceSafe Road Map and between-the-lines reading of a VSS transcript, Visual Source Safe is targeted towards individual developers or small teams (1-5) with lightweight SCM needs. Microsoft is encouraging everyone else to migrate to the more sophisticated Visual Studio Team System. And Its Team Foundation Server (TFS) Version Control

Features of TFS Version Control
  1. Atomic Checkin
  2. Work Item Integration
  3. Checkin Policies
  4. Shelving
  5. Delta File Storage & Delta Binary File Storage
  6. Large File Support (>4GB)
  7. Distributed Team Support
  8. E-mail Check-in Notification
  9. Non-Windows Support
  10. Diff Tool Extensibility
  11. Shared Checkout
  12. VS 2003 Integration

VSS does not have:

  • Workspaces
  • Changesets
  • Shelvesets
  • XML Diff/Merge Tool
  • Content Merge, Namespace Merge (branch)
  • Auditing
  • Locking
These are Some Numbers to show you the Big Difference:
In a project the repository was made up of just under 6,000 files making up around 250Mb and using a good WAN Connection to the server:
To make a Full get on source tree:
VSS - 1 hour 26 mins 53 seconds
VSTS - 7 mins 32 Seconds
To make a Get Latest when nothing changed (on full source tree):
VSS - 14 mins 23 seconds
VSTS - 3 seconds
To make a Right click on a folder:
VSS - 3.5 seconds
VSTS - Instant
To make a Navigate down a folder with no files in it:
VSS - 4.5 seconds.
VSTS - Instant
Show files checked out to me:
VSS - 3 mins
VSTS - Instant

At the End if you still insist to use Visual SourceSafe please Read this Choosing Between Microsoft Visual Studio Team System and Microsoft Visual SourceSafe

kick it on DotNetKicks.com
Post a Comment