SourceGear Vault 5.0.2 is a maintenance release for Vault 5.0. If you have not upgraded to Vault 5.0, see sourcegear.com/vault/releases/5.0.html for more information.Installation Notes

Please ensure you have a verified backup of your database before upgrading, and upgrade at a time when it is convenient to not have access to the server. On very large Vault installations, the upgrade may take several hours.

Vault 5.0 does not support Dragnet integration. Users requiring integrated work item tracking should investigate SourceGear Fortress. Fortress is an integrated solution for application lifecycle management (ALM), including work item tracking and work item clients integrated into Visual Studio and Eclipse.

Vault 5.0 is not backwards compatible with previous versions of Vault. In essence, Vault 5.0.x clients will only interact with Vault 5.0.x servers and vice versa. Vault 2.x, 3.x, and 4.x clients and servers are not compatible with Vault 5.0 clients and servers.

For details on Vault licensing, including upgrade policies and demo keys, please see the Licensing FAQKnown issues:

Important note when upgrading from the 4.0.6 release: There was a bug in the uninstall routine for the 4.0.6 for users who installed the server and the client together using the server's installer. Upgrading in that situation will succeed, but leave two client shortcuts on the desktop. Please follow the instructions at support.sourcegear.com/viewtopic.php?t=9653 for instructions on removing the 4.0.6 server and client before upgrading.

When using the VS Enhanced Client's "Open From Vault" functionality in Visual Studio 2008, you will not be able to open solutions that have not yet been upgraded by Visual Studio to the Visual Studio 2008 format.What's New Since Vault 5.0.1:

Visual Studio Enhanced Client

* Fixed a rare Visual Studio freeze during a get latest operation * Fixed case where checkout could be performed on an old version * Fixed case where files modified outside of Visual Studio could be unintentionally reverted on commit * Fixed a crash when modifying a newly added resource file

Eclipse

* Fixed occasional Byte Order Marks inserted in source files. * Removed the requirement that all projects be open

Shelve

* Shelve failure when shelving an add operation, when the item already existed in the repository

* There is now a Security Reporter Power Toy that will export repository access and folder security settings for all users.

WebDav

* Entering bad login credentials now returns a HTTP 401 error

Installer

* Fixed a case where an uninstalled client would cause Visual Studio to display an error on startup

Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 5.0.2 client should be connecting to a 5.0.2 server). 5.0.x clients are able to communicate with any 5.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 5.0.x clients and servers are not compatible with 1.x, 2.x, 3.x or 4.x clients and servers.Upgrading 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.