3.1.7 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:

3.1.7 Release Notes

Post by dan » Mon Jan 30, 2006 3:11 pm

3.1.7 is primarily a preview release of a Dreamweaver IDE client, but there are a few other minor updates as well, especially for NAnt/Cruise Control integration tasks.

If you have not upgraded to any 3.1 Vault version, see http://support.sourcegear.com/viewtopic.php?t=4294 for more information.


The following changes are included in this release:

GUI Client Only
- Diff against a local folder from Show Labels now allows you to browse to a local folder.
- Addressed issue in Merge Branches where "Attempt to checkout files failed" message was displayed without further information.

Server Only
- Show Labels now returns label in the correct order by date if the labels were created with a VSS import.
- Deadlocks caused by too many CC.NET simultaneous logins now addressed.
- Fixed FailFileStreamError problems on BeginVersionHistoryQuery when CLC is invoked from CC.Net.

NAnt/CC.NET Integration
- NAnt task documentation is now included with the release.
- NAnt Checkin task no longer converts binary file's EOL.
- NAnt checkin on folder no longer returns "Invalid object version specified"
- NAnt checkin task's "diskfile" attribute now works.


Client/Server Version Compatibility
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.1.x clients are able to communicate with any 3.0.x or 3.1.x server, but specific bug fixes will not work correctly if they required both client and server changes. 3.1.x clients and servers are not compatible with 1.x or 2.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.

Important: If you are upgrading from a pre 3.1 version of Vault, the server installation will take longer than normal because the database needs to be converted to a new format.

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

Post Reply