In this article I am trying to make clear the concept of Microsoft Visual SourceSafe.
Microsoft Visual SourceSafe
Microsoft Visual SourceSafe is given the permits of different organization to work on many project versions at a time; Visual SourceSafe is a control system which is control the file level versions. Basically it is beneficial for software development environment, where it is used in maintaining parallel code versions. It is supports cross-platform development with allow cooperative editing and sharing of data. Visual SourceSafe is designed for handle the tracing and portability issues involved in maintaining one source control base.
With the Visual SourceSafe, it is provided the help to protect your team from accidental file loss. Allow back-tracing to earlier versions of a file. It is supports branching, sharing, merging, and management of file releases. Tracks modular code (one file that is reused, or shared, by multiple projects).
Compatibility and Version
The current release of Visual SourceSafe is fully compatible with database versions 6.0 and earlier. The new version of VSS is Service Pack 6 for Visual Basic 6.0, Visual C++ 6.0 with Visual Source Safe 6.0d, The last release was Visual SourceSafe 2005. Since then, in Dec. 2007, there was a Visual SourceSafe 2005 Update release, and also a "hotfix" in Nov. 2009 which improved interoperability with Visual Studio 2010.
Version Control and File Sharing
The Visual SourceSafe provides the immediate and efficient sharing of files amongst projects. The collections of files in projects make team coordination intuitive. If you want to add the file in Visual SourceSafe the file is automatic stored in the database and which is available for other users. And after changes in file it is saved so that if any user can recover an old version of file any time, Members of your team can see the latest version of a file, make changes to local file copies, and save new versions in the database. When a set of files is ready to deliver, Visual SourceSafe makes it easy to share and obtain different versions of the selected set of files.
In the Visual SourceSafe, you can write extensions based on Visual SourceSafe as needed for your environment. Extensions are usually provided in the form of stand-alone applications written to the automation interfaces.
Many developers are accessing Visual SourceSafe functions from their development environments with the help of third-party programs. We can easily integrated Visual SourceSafe with Visual Studio and other development tools, such as Microsoft Access. Visual SourceSafe supports a developer environment in many ways by allowing:
· Setting of folder policies to enable group development scenarios.
· Tracking of programming modules to allow reusable or object-oriented code
· Bug fixes
· Configuration of new projects for isolated Web development
· Addition of a new Web developer to an existing team Web project
· Automation of source code control events
· Easy transition to a new release of an existing project
· Batch/nightly builds
· Access to automation interfaces
· Source control over slow connections