3.1.2 Release Notes

[dan]

3.1.2 is a maintance 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
· Ability to check and uncheck all actions has been added to the History Actions screen in the History Query dialog.
· Diff command now works properly when invoked from the History by Version Details dialog.
· Version Check option now applies only to whether to connect the SourceGear version check server, and not to displaying version information on startup.

IDE Client
· IDE now honors setting that requires a bug ID to be entered for a checkin.
· Specifying login and connection info in the IDE no longer changes the default login settings in the Vault GUI client.
· Opening the Vault GUI client from within the IDE now works properly when a debug log is being used.

Admin Tool
· Email settings now display error when the the password can't be decrypted for any reason.

Command Line Client
· Labels are no longer case senstive when using the GETLABELDIFFS command.
· Password is now encrypted when stored via the REMEMBERLOGIN command.
· Repository is no longer a required option in the REMEMBERLOGIN command.

Server Only
· History is now returned on a folder with inherited security rights where User rights would override Group rights.
· Ending a transaction has been sped up from 3.1.0 release.
· Reduced number of SQL deadlocks during Refresh and other operations, speeding up transaction processing.

Installation
· Passwords with spaces in them now get copied to web.config properly

<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.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.


<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.

<b>Important</b>: 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.