Vault 3.0.2 Release Notes

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear

Post Reply
dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Vault 3.0.2 Release Notes

Post by dan » Fri Jan 21, 2005 2:11 pm

The following features and changes have been included in the 3.0.2 release:
<UL>
<b>Installer</b>
<LI>Improved many aspects of server installation, including installation on 2003 systems, domain controllers, and non-english systems.

<b>IDE Client</b>
<LI>Intermittent error when trying to load a solution with large numbers of projects has been fixed.
<LI>Error message that an .aspx file is already checked out no longer appears when checking out a .vb file whose associated .aspx file is indeed already checked out.

<b>Diff/Merge Tool</b>
<LI>In rare instances a manual merge would not move a text block to the middle pane correctly. This has now been fixed

<b>Client Only Changes</b>
<LI>Edit comment button in Version Details screen is now enabled only for the user who checked in the change, or the Admin user
<LI>Rollback from file version prior to a branch is no longer allowed.
<LI>Timeout for initial connection to Vault server is now 90 seconds, rather than 2 hours.

<b>Server Only</b>
<LI>Exception has been fixed when moving a folder to a path to which it was previously shared


<b>Admin Tool</b>
<LI>File exclusion list now no longer lists .csproj files by default.
<LI>The email settings dialog can now be displayed, even if <EmailAllowedEndings> is missing from vault.config,


</UL>

<b>Client/Server Version Compatibility</b>
It is always recommended that your client and server versions match exactly (e.g., a 3.0.1 client should be connecting to a 3.0.1 server). 3.0.x clients should be able to communicate with any 3.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 3.0.x clients and servers are <b>not</b> compatible with 1.x or 2.x clients and servers.

<b>Upgrading From Previous Versions</b>
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.

Post Reply