3.1.6 Release Notes

[dan]

3.1.6 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
- LogFilePath is no longer required in an app's config file in order to do client logging.

Server and Client Changes
- Various EOL fixes related to Mono/Unix.

Server Only
- Label events should appear at the top of the changeset when viewing history.

IDE Client
- IDE no longer performs the version check.
- Rebinding a web project that has been converted from VS 2003 to 2005 will have an "Invalid Handle" error message, but it is no longer stuck in an infinite loop.
- Double-clicking on an aspx.cs file using VS 2005 no longer displays an error message about the file already being checked out.

Command Line Client
- Now prints version number at top of help command.
- Added VERSIONHISTORY command to retrieve history by version
- Can now label a file or folder at a particular version.
- Can now specify a -workingfolder option for Get and GetVersion that sets a temporary working folder during the CLC Get command.
- Added -backup option to GET, GETWILDCARD, CHECKOUT, GETLABEL, and GETVERSION commands, that overrides the user's default setting for whether to backup a modified file on a Get.
- Get on non-windows platform no longer places <feff> at the start of a mergeable file.
- Updated -destpath parameter help to make it more clear this is a non-working folder option.
- DIFF command help has been updated.
- An error message is now displayed if logout fails due to invalid login.

Installation
Installer writes sgvaultuser in impersonation for web.config if impersonation and sql auth are both specified.


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.