VSS ( Visual source safe)

December 22, 2006 at 11:05 am 1 comment

Microsoft Visual SourceSafe is a source control software package oriented towards smaller software development projects.It is similar to CVS.

Like most source control systems, SourceSafe creates a “virtual library” of computer files. Users can read any of the files in the library at any time, but in order to change them, they must first “check out” the file. They are then allowed to modify the file and finally check it back in. The changes are made available to the other users only after the file has been checked in.

Most often used for source code, SourceSafe can actually handle any type of file in its database, but prior versions have been shown to destabilize when confronted with large amounts of non-textual data (images, binary executables, etc). It is not yet clear whether the latest version has improved in this respect.


1.) Visual SourceSafe’s advantages are relative ease of use and some degree of integration with other Microsoft development solutions.

2.) For small or medium scale development, where multiple versions are not simultaneously supported, its limitations do not cause major problems.

3.) Further strong points include its excellent integration with Microsoft Visual Studio, its easy-to-use interface, and the fact that it is included as part of certain MSDN Subscriptions.


1.) Some programmers feel that it is sluggish, causes system instability and is missing features taken for granted on newer revision control systems. The perceived sluggishness of SourceSafe depends greatly on the environment in which it is set up. In single user and small team LAN configurations, it can be reasonably fast.

2.) The instability criticism is rooted in the fact that Visual SourceSafe uses a file based archive architecture in which any client can update a file in the archive after “locking it”. If a client machine crashes in the middle of updating such file, the file could become corrupted. Many users of Visual SourceSafe get around this limitation by regularly backing up the database and using the utility provided with Visual SourceSafe which checks the database for corruption and can fix certain erro


Entry filed under: technical.

Happy Christmas Google Notebook

1 Comment Add your own

  • 1. Sulo  |  December 22, 2006 at 11:15 am



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed

December 2006
    Jan »

Blog Stats

  • 249,923 hits

Java software

Flickr Photos

%d bloggers like this: