• Vault
• SourceOffSite
• DiffMerge

• Support Forum
• Customer Service Portal
• News and Announcements

September 2004

SourceGear Vault is a source code control system designed specifically to replace Microsoft Visual SourceSafe. Vault is built on Microsoft SQL Server and .NET with a design that emphasizes reliability, network integration and openness.

Installation Requirements

The SourceGear Vault server requires either Windows 2003 Server or Windows 2000 Server (SP3) with the .NET Framework 1.1, IIS 5.0 or greater, and either Microsoft SQL Server 2000 or MSDE 2000.

The SourceGear Vault clients require at least Windows 2000 or Windows XP with the .NET Framework 1.1.

Upgrades from Previous Versions

It is recommended that you backup your Vault database prior to an upgrade. This can be done from either the Vault Admin tool, or the SQL Enterprise Manager tool.

To upgrade from a previous installation of Vault, simply invoke the new installer, and choose the same options that were selected when Vault was previously installed. Program files and configuration settings will be automatically updated to reflect the upgrade. Note that the server installation will not delete your database unless you explicitly tell it to.

You may also safely uninstall Vault first, and then install the upgrade. As with installation, an uninstall will not delete your database unless you explicitly tell it to.

NOTE: The Vault 2.0 server cannot be upgraded from a Vault 1.0 server installation (which includes Vault 1.0.1, 1.0.2 and 1.0.3), due to changes in installer technology. The Vault database can be upgraded, but the server installation itself cannot.

If you are currently running Vault 1.0, you can first upgrade from Vault 1.0 to Vault 1.1 or 1.2, and then upgrade to 2.0. Additionally, you can uninstall Vault 1.0, and then install Vault 2.0 as a new installation. Be sure to not delete your database when uninstalling, and to choose the existing database on the fresh install.

Release Contents

The programs included as part of Vault include:

1. Vault Server (VaultService.asmx). This is actually a .NET Web Service installed in an IIS virtual directory. It uses SQL server to store the source control files, and accepts connections from Vault clients.


2. Vault GUI Client (VaultGUIClient.exe). A Windows .NET client that connects to the Vault Server and allows users to locally manage files under source control in a windowed application.


3. Vault Command Line Client (vault.exe). A command line client that supports many of the commands the GUI client supports, allowing the user to connect to the Vault Server via scripts or without user intervention. This client still requires the .Net framework in order to run.


4. Visual Studio IDE Integration DLL (VaultIDE.dll). Allows Vault to be the source control provider in Visual Studio .Net, VC6, and VB6. Note that this uses the Microsoft MSSCCI interface to integrate with Visual Studio, and is therefore limited in functionality to what MSSCCI allows. The GUI client is recommended for a more full-featured interface.


5. Vault Admin Tool Client (VaultAdmin.exe). A Windows .Net client that allows the user to configure the Vault Server and its repositories.


6. SourceSafe Import Tool (VSSImport.exe). A wizard that creates Vault repositories from existing Visual SourceSafe databases (or parts of them). This wizard supports import of file history, labels, and additionally shares and pins files in Vault as they are in VSS.

Install Packages

These programs are included in the following installation packages:

1. Server Installer:
• Vault Web Services DLLs
• Admin Tool (optional)
• GUI Client (optional)
• Command Line Client
• Visual Studio IDE Integration DLL
2. Client Installer:
• GUI Client
• Command Line Client
• Visual Studio IDE Integration DLL
3. Admin Tool Installer:
• Admin Tool
4. VSS Import Tool:
• VSS Import Tool

License Numbers

Vault requires a demo license before any user other than Admin can log in. If you downloaded Vault from our website, you should have received a license number by email. If you do not have a license number, go to:
http://www.sourcegear.com/vault/downloads.html
and select the "Demo Serial Number" link. This will automatically send you a license number for use in demoing Vault. Once you have a license number, login into the Admin Tool (using the "Admin" login and password that was specified during installation), and add the license number using the Licenses Tab.

ASP.NET Configuration

When running the Vault server on a machine with IIS 5.0, Vault users may wish to modify the responseDeadlockInterval parameter in the ASP.NET machine.config file on the Vault server machine. In its default configuration, ASP.NET assumes that an application is deadlocked if it requires more then three minutes to respond to a request. Under certain situations, ASP.NET may terminate the Vault server application if an operation requires more than three minutes. When this happens, ASP.NET will make an entry in the Application section of your Event Log:

aspnet_wp.exe (PID: xxx) was recycled because it was suspected to be in a deadlocked state. It did not send any responses for pending requests in the last 180 seconds.

This problem can be avoided by changing the responseDeadlockInterval to a longer time duration. Note, however, that this configuration parameter affects all ASP.NET applications on the server machine.

We recommend running the SourceGear Vault server on a dedicated machine with ASP.NET configured with a responseDeadlockInterval of one hour. This configuration is not strictly required, and may not be necessary for many users. If you choose to run the Vault server on a machine which is shared by other ASP.NET applications, you may wish to try using Vault with the responseDeadlockInterval unchanged.

To change this parameter, locate your machine.config file:

c:/WINNT/Microsoft.NET/Framework/v1.1.4322/CONFIG/machine.config

Within that file, locate the processModel element. On that element is an attribute called responseDeadlockInterval. To change this value to one hour:

responseDeadlockInterval="01:00:00"

Support and Contact Information

There are a number of ways to get access to Vault support:

1. The SourceGear Vault documentation page at http://www.sourcegear.com/vault/documentation/ contains support resources, such as troubleshooting guides, tech notes, and FAQs.
2. A public forum exists at http://support.sourcegear.com where you can ask questions of the Vault community, and search a knowledge base for answers to common problems.
3. Use the Help->Technical Support Menu item to send an email to SourceGear’s support department for any installation or usage issues concerning Vault.

Any questions regarding pricing or sales can be emailed to store@sourcegear.com

Support for Vault is available from 9am-5pm Central Time Monday through Friday.

Changes for 2.0.6

The following changes have been made in the 2.0.6 release:

• Client status search pane now works with .Net framework 1.1 SP1
• The server and client is now compatible with .Net framework 2.0 Beta
• A folder getlabel from the command line will now get file labels of the same name underneath that folder

Changes for 2.0.5

The following changes have been made in the 2.0.5 release:

• Client now has logging capabilities. See http://support.sourcegear.com/viewtopic.php?t=1534 for more details
• Fixed mutex error that would happen intermittently in Vault clients.
• Fixed mutex-related Shadow folder errors when there were multiple shadow folders defined.
• Fixed incorrect error message when user logs in with an invalid account name.
• The repository list in the admin tool is now sorted in the same way it is sorted in the database (fixing a problem where spaces and dashes were sorted differently and caused a problem on which row was being viewed).
• Fixed error with default rights and label security when viewing an inherited label.
• Fixed error with cookie handling while downloading files on some systems.

Changes for 2.0.4

The following features and changes have been included in the 2.0.4 release:

• The IDE client can now be used with Whidbey versions of Visual Studio.
• Performance for determining tree deltas on the server has been greatly increased (especially when the tree version being requested is no longer in the server’s RAM cache).
• Implemented a login delay when a user fails to login on consecutive attempts.
• Showing a label with a very long comment now works properly.
• Showing labels for users with no default rights now works properly.
• A local refresh is now done before the Commit dialog is displayed, to ensure the status of all files is up to date.
• If a baseline file has the wrong contents (because it has been edited inadvertently by the user), the client now requests a new baseline file to apply changes to and from.
• Fixed bug where a checkout list was not generated properly when a local path is greater than 256 characters.
• Fixed bug where performing a diff from history against another repository file resulted in the target file having a version of 0.

Changes for 2.0.3

The following features and changes have been included in the 2.0.3 release:

• “Revert” is now the default option for Undo Checkout.
• Network configuration options are now available from the options dialog.
• Checkin of files that were modified in date only has been sped up considerably.
• The Auto Merge dialog no longer misreports the number of conflicts during the auto-merge.
• The Auto Merge dialog now has default focus on OK button
• The Command line client now support begin and end date on history queries, as well as ability to specify non-recursive queries, and sorting by date
• The Command line client now allows pinning the latest version of a file or folder without having to know the specific version number.
• Projects that are re-used in multiple solutions now have the correct bindings.
• The IIS Timeout and maximum file upload values are now validated in the Admin Tool.
• If you choose to run the Vault Service with a Windows account during the install, the password is no longer output to the installer log file.
• Dialogs are now guaranteed to be on-screen when they are invoked (going from dual to single monitor should work correctly now)
• More database space is reclaimed on repository deletion.
• Performance has been increased on Delete and Rename operations when security is on.
• Performance has been increased on getting the checkout list when security is on.
• FailDBReader problem when invoking history on a shared folder with security turned on has been fixed.

Changes for 2.0.2

The following features and changes have been included in the 2.0.2 release:

• Shared files are now handled properly during a Merge Branches operation.
• Merge Branches no longer outputs “Attempt to Retrieve Files Failed” when the files were actually retrieved.
• Added more information to Add To Source Control dialog and Open From Source Control dialogs in the IDE to make clearer which projects and working folders are being processed.
• The Prompt Before Overwrite option when accessed from the IDE options now reflects the real value.
• Admin tool Folder Security tab now displays correct permissions when a user or group has different permissions on the same path in different repositories.
• Command line client now accepts non-default ports.
• Command line client Getlabel of a folder that contains a shared item now outputs an informational message when the extra parameter that specifies which path to use is not specified.
• Command line client now outputs parameters in correct order on getlabel of a folder that contains a shared item.
• Upgrading previous Vault databases where a file label was duplicated on multiple versions of the file now upgrades properly.
• Spaces now trimmed out of bug integration URL in admin tool.
• Item comments that are only white space are stripped before committing.

Changes for 2.0.1

The following features and changes have been included in the 2.0.1 release:

• Installer bug fix where it would fail on an index/count exception.
• Speedup on checking out files when there are a large number of checkouts and security is turned on.
• Get on a single file labeled file to a non-working folder now works properly
• Speedup of Get on a label when the folder being retrieved is a subfolder of where the label was applied.
• Timeout on delete of a repository has been increased.
• Web client now accessible from server home page
• Getting of a label from command line client no longer requires setting a label working folder – it now takes an extra parameter in the GETLABEL command to specify the working folder to get to.

Changes for 2.0

The following features and changes have been included in the 2.0 release:

• Completely new and expanded diff/merge utility.
• Shadow folders
• Lightweight labels
• Snapshots (Vault 1.x labels are still supported and called “snapshots”)
• Login profiles
• Unix Command Line Client, using the Mono framework.
• Lots of updates and bug fixes to the Command Line Client, to make it usable as a standalone client, instead of as a scripting tool.
• Merge Branches now merges in both directions (from branch to trunk or trunk to branch)
• Ability to show differences against labels, local files, and arbitrary repository files.
• Support for external merge applications.
• Repository security (the ability to hide an entire repository from users).
• Now only active users can be shown when in the Admin Tool
• Client can be set to prompt user before overwriting file
• Client can be set to not backup files that get overwritten by client
• Global option for what to do when undoing a checkout.
• Support for proxies which require authentication
• Can now copy from pending change set and status search panes
• Better messages on failed connections
• Check In dialog now only lists files within the folder it was invoked on.