3.1.8 Release Notes

[dan]

3.1.8 is a maintenance release for 3.1. 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
- Intermittent cases of file being checked out and renegade have been resolved.

Server Only
- Moving a file in large repository with a very large number of shares handles memory more efficiently.
- The query returned in Show History on a branched file now returns the labels in the correct order.
- Some labels were displayed in history not at the version date of the item, but the version date of the parent where the label was applied. Labels now always display in history at the version the label was applied to.

Visual Studio IDE Client
- Create New Folder button now available when adding a project to source control.
- Can no longer checkin a file from a machine that is different from the one where it was checked out.

Dreamweaver IDE Client
- Can now move and cut/paste files and folders from one folder to another, and have the move reflected in the Vault repository.
- Set Working Folder dialog has been re-designed to allow the user to create a new Vault folder and to more easily name and place the project within Vault.
- Local working folder is no longer blank in the Set Working Folder dialog in DW 2004 version 7.0.
- Projects can now be added at the root Vault folder without an error message being displayed.
- Using the Put command as a Checkin command now works.
- Status of files after an initial Put where sometimes Unknown, which caused problems checking them out. All files should now have a blank status after a Put.

Diff/Merge Tool
- Escape key will now close the diff/merge application.
- Option now exists to not display dialog that says files are identical.

NAnt and Cruise Control .NET Integration
- Reduced client-side cache file contention experienced by some CruiseControl.NET users.
- Additional improvements to server-side contention on login sometimes experienced by CruiseControl.NET users.


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.