Vault 4.0.5 Release Notes

[jeremy_sg]

SourceGear Vault 4.0.5 is a maintenance release for Vault 4.0. If you have not upgraded to Vault 4.0 version, see
http://www.sourcegear.com/vault/releases/4.0.html for more information.

Known issues:

There is now an automated tool to convert projects and solutions bound to the Visual Studio 2003 compatible client to the new Visual Studio 2005 client. You can download that tool from:
http://support.sourcegear.com/viewtopic.php?t=8214

If you wish to convert your solutions and projects manually, follow the steps outlined at:
http://support.sourcegear.com/viewtopic.php?t=7937

The following changes are included in this release:

General Client Issues

* Checkin fails when user edits checked out file and edits baseline. Baseline is not corrected as it should be.
* Automerge sometimes broke file encodings
* Deleted objects list in folder properties was displaying incorrectly.
* VaultClientIntegrationLib is now signed.
* Eclipse client now handles HTTP proxies.
* NAnt: Added a comment attribute to the vaultcheckin task
* NAnt: Added the ability to add a directory to the vaultadd NAnt task

Visual Studio 2005 client Fixes:

* Change Bindings Dialog: Added a new dialog to provide an interface to configure Binding and Online properties for individual projects and solutions.
* Add to Vault: Now supports more situations where the project is not in a subfolder of the solution.
* Double Get: It is no longer necessary to perform two get operations when a new file has been added to a project.
* Web Site Projects: The bin/ directory should no longer be added to source control.
* Numerous fixes for uncommon project types.
* Automatically checked out files are now added to pending change list immediately.
* Open From Vault now works on solutions having multiple web site projects.
* Context Menu items were not showing up for subordinate files (*.designer.cs for example) - new change since beta.
* Add solution no longer attempts to add web site bin folder contents - new change since beta.
* A save-all operation is forced before performing commands in the pending change view. This prevents cases where a solution files were not being checked in because it had been changed, but not yet saved. - new change since beta.

Server:

* Backup and Restore fixes.
* Some checkouts were being duplicated, which could only be undone by using the admin tool.
* Groups would sometimes show up twice.
* Repository Admins could not obliterate
* Performance for the admin tool was very bad for installs with many users and many repositories.

Client/Server Version Compatibility

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

Miscellaneous

Also, the client install will upgrade client cache files to a new format if you are currently on a pre 4.0 release. This will not affect upgrade times, but also will not allow you to revert back to a pre 4.0 client without losing client state information.