Vault 3.1 Beta 1 Release Notes

[dan]

A server upgrade from Vault versions prior to Vault 3.1 will require more upgrade time than previous Vault upgrades, because the database needs to be converted to a new format. Make sure you backup your database before upgrading, and upgrade at a time when it is convenient to not have access to the server for up to an hour.

Vault 3.1 Client upgrades will convert all of the client cache files to a new format. This will happen automatically and will not affect upgrade times, but means that you cannot revert to a pre 3.1 client without losing all your client state information.

The following features and changes have been included in this release:

General
· Added support for .NET framework 2.0 (beta 2).
· Vault now works with SQL Server 2005 (Yukon).
· Vault DLLs now use strong names.

Client Only
· You can now choose the location on disk for the client cache folders, working folder state/baseline folders and backup folders.
· The history transaction details dialog now displays the full repository path for the transaction items.
· You can now view the differences of a file or folder from the history transaction details dialog.
· Fixed problem that caused duplicate files and folders to appear in file list.
· Improved commit performance on large change sets.
· Improved performance on adding and updating multiple files.
· History query filtered by date now displays the full path to the item.
· Non-binary files are no longer read-only after the initial get when the local file option is set to make binary files read-only.
· Working folder scanning message is now correctly displayed the entire time the working folders are scanned.
· Keywords now correctly updated on check-ins of unmodified files.
· Check-In button on toolbar now correctly enabled.
· Fixed handle leak in shadow folders.

Server Only
· Fixed problem that caused repositories to no longer be visible in some cases after a checkin of an invalid folder version.
· You can now specify which repositories a Vault Server serves in the Vault.config file.
· Optimized stored procedures for better concurrency.
· Improved label performance.
· Improved performance on committing modified files.

Admin Tool
· Admin tool now remembers its size and screen location.
· Fixed error that occurred when viewing email settings when <EmailAllowedEndings> was missing from Vault.config

IDE Client
· Added support for Visual Studio 2005 (beta).
· Unmodified files are no longer checked in when the "Check In unchanged files" IDE option is set to undo checkout.

Bug Tracking Integration
· You now have the option to view all open Dragnet items from the My Open Items dialog.
· You can now edit Dragnet items from within Vault (you must be using Dragnet 1.0.3 or greater for this feature).
· Added option to the Admin Tool to force users to enter a valid Dragnet Bug Tracking ID during a Vault checkin.

Command Line Client
· Command Line Client now works with Mono on OS X.
· Added a “helphtml” command that displays the command line client help in HTML format.

Vault Web
· The show differences page now honors security rights.

Client Installer
· MSVCR71.dll now gets installed to the client directory so the diff merge tool works on machines that do not have this DLL installed.


Vault 3.0 clients are compatible with Vault 3.1 servers and vice versa. Vault 2.0 clients and servers are not compatible with Vault 3.1 clients and servers.