Vault 4.0.2 Release Notes

Post by **jeremy_sg** » Fri Jul 06, 2007 3:52 pm

SourceGear Vault 4.0.2

SourceGear Vault 4.0.2 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 are still issues which prevent using projects in the Visual Studio 2005 IDE Client which are bound to source control in a solution which is not bound. If you use this configuration, please remain on the 2003 compatible client until these issues have been resolved.

It is still recommended that users who are converting solutions and projects from the Visual Studio 2003 compatible client to the Visual Studio 2005 client follow the steps outlined at: http://support.sourcegear.com/viewtopic.php?t=7937

The following changes are included in this release:

Visual Studio 2005 Client Only

* Deleting a file wasn't working in Web Site projects.
* Some project types were throwing "not implemented" errors.
* Line history was broken for branched files.
* When a visual studio build is invoked from the command-line, treat project/solution as offline.

General Client issues:

* A change to the Command Line Client's history command output broke Cruise Control.Net integration
* The output from the Command Line Client's LISTFOLDER command is now recursive again, as it was in 3.5.

Server Issues:

* The Server install was not setting database permissions correctly on upgrades using SQL Server authentication.

Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 4.0.2 client should be connecting to a 4.0.2 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.