Visual SourceSafe 2005 from Microsoft

Visual SourceSafe provides individual developers and small development teams with tools to make safe alterations to existing code and track changes across users, projects, and time.

Visual SourceSafe is a version control system product that delivers restore point and parallel collaboration capabilities, thus allowing application development organizations to work on several versions of software simultaneously. The version control system introduces a check-in and check-out model in which an individual developer checks out a file, makes changes, and then checks the file back in. Other developers typically are not able to make changes to a file while it is checked out. Source code control systems also allow developers to roll back or undo any changes that later create problems.

Visual SourceSafe is a version control system that:

• Protects users from accidental file loss.
• Allows back-tracking to previous versions of a file.
• Allows branching, sharing, merging, and management of file releases.
• Tracks versions of entire projects.
• Tracks modular code (one file that is reused, or shared, by multiple projects).
• Individual developers and small development teams have found that they can benefit from the peace-of-mind and productivity benefits that version control provides. Visual SourceSafe is a version control product, focused primarily on maintaining file change histories, audit trail logs, and disaster recovery for source code files. It is most effective for small, geographically close teams who generally work on a high-speed, low-latency Local Area Network (LAN) in a highly trusted environment, and whose shared development assets are unlikely to exceed 4 gigabytes (GB). Visual SourceSafe is a client-only file-server application that does not require server-side processes or code execution.

• Remote Web Access over HTTP. Use Visual Studio to connect to Visual SourceSafe databases from anywhere in the world where HTTP or HTTPS Web access is available. (Requires Visual Studio 2005, IIS, and ASP .NET).
• Enhanced Performance and Stability. Work faster with significantly improved LAN access speeds, particularly when using Visual SourceSafe along with Visual Studio in slow and remote RAS configurations. While maintaining the compatibility of its current client-based file share architecture, Visual SourceSafe provides significantly faster access speeds for common operations, particularly improving performance in slow and remote network situations. Robust improvements reduce the need to analyze, administer, and repair databases.
• Increased Capacity. Data storage is increased to 4 GB, and archive limits are also enlarged.
• Regional Time Zones and Languages. View file change histories adjusted to your local regional time zone while maintaining a separate audit log of changes synchronized to the server reference clock. Customize the user interface with any specified language and font.

• Support for Custom Viewers, Merge Tools, and Editors. Use the new plug-in editor/viewer feature to compare and view source code and document differences using any third party or custom tool.
• Managed Code Extensibility. Use the .NET Programmable Interop Assemblies (PIA) for Visual SourceSafe automation to further extend Visual SourceSafe with new functionality that can be developed using Visual C#® and Visual Basic® .NET.
• Automate Your Team Processes. Use events, such as OnBeforeCheckout or OnAfterCheckIn to automate your process. Leverage the new MSBuild tool by creating custom tasks that retrieve and download source code files before building them with an automated build.

• Unicode and XML Support. When developing ASP.NET Web services with previous versions of Visual SourceSafe, all XML files such as Web.config, *.wsdl, *.disco, *.map, and others were stored as a binary format in Visual SourceSafe. This meant that only one developer at a time could modify or check-out those files, limiting the possibilities for parallel development tasks. Also, Visual SourceSafe could not be used to compare or merge those XML files stored as binary. Using Visual SourceSafe 2005, developers can now store, compare, and merge UTF-8 and Unicode-encoded file content, including XML files. Using the multiple check-outs functionality, developers can simultaneously work on parallel development tasks and merge the results.
• Check Out Improvements. Visual SourceSafe and Visual Studio are even better together through continued innovations to the integrated source code control experience in Visual Studio, including the ability to check out a file from a local Working Folder directory without requiring the network download of the latest version of the file from the Visual SourceSafe database. Within Visual Studio, check outs are now automatic and prompting is reduced.
• Web Project Enhancements. Take advantage of greater flexibility in specifying project locations, and synchronize renamed or deleted files within Visual Studio. Open and browse source-controlled projects using the standard Open Project dialog.

• Processor:

• Operating System:

• Hard Disk:

• Memory:

• Optical Drive:

• Other: