Release Notes for Vault 4.1.0

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear

Post Reply
jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Release Notes for Vault 4.1.0

Post by jeremy_sg » Wed Feb 20, 2008 3:05 pm

SourceGear Vault 4.1

We are proud to present SourceGear Vault 4.1. With new and enhanced features, SourceGear Vault 4.1 is considered a maintenance release, and is a free upgrade for users who have purchased Vault 4.0.

• New customers can purchase Vault client licenses at the SourceGear Store.

• Note, Vault 1.x and 2.x license numbers cannot directly be upgraded to a Vault 4.1 license. Vault 1.x and 2.x licenses will need to be upgraded to a Vault 3.1 license. The resulting license can then be upgraded to Vault 4.1.

Installation Notes

• Please ensure you have a verified backup of your database before upgrading, and upgrade at a time when it is convenient to not have access to the server. On very large Vault installations, the upgrade may take several hours.

• The two IDE clients have been renamed. The "Visual Studio 2003 Compatible Client", will now be know as the "Classic Client", since it offers support in more Visual Studio versions than 2003, and supports more IDEs than just Visual Studio. Similarly, the "Visual Studio 2005 Integration Client" will be known as the "Visual Studio Enhanced Client". The new name reflects the fact that it supports 2008 as well as 2005.

• Vault 4.1 does not support Dragnet integration. Users requiring integrated work item tracking should investigate Fortress. Fortress is an integrated solution for application lifecycle management (ALM), including work item tracking and work item clients integrated into Visual Studio and Eclipse.

• Vault 4.1 is not backwards compatible with previous versions of Vault. In essence, Vault 4.1 clients will only interact with Vault 4.1 servers and vice versa. Vault 2.0, 3.0, 3.1, 3.5 and 4.0 clients and servers are not compatible with Vault 4.1 clients and servers.

Known issues:

Important note when upgrading from the 4.0.6 release. There was a bug in the uninstall routine for the 4.06 for users who installed the server and the client together using the server's installer. Upgrading in that situation will succeed, but leave two client shortcuts on the desktop. Please follow the instructions at http://support.sourcegear.com/viewtopic.php?t=9653 for instructions on removing the 4.0.6 server and client before upgrading.

When using the VS Enhanced Client's "Open From Vault" functionality in 2008, you will not be able to open solutions that have not yet been upgraded by Visual Studio to the Visual Studio 2008 format.

Web Site projects with large numbers of files or files accessed via a network will still suffer from some performance problems.

New Functionality

• Visual Studio 2008 support. This is the first version of Vault that offers integration with Visual Studio 2008.

• Legacy IDE options. Users requested a few options available in the Classic Client be implemented in the VS Enhanced Client. The two options that have been implemented are Get Latest when a solution is opened and Check In when a solution is closed.

• VS Enhanced Context Menus. The VS Enhanced Client’s context menus were rearranged in order to provide easier access to commonly used operations.

• Better progress indicators In the VS Enhanced client. The Add Solution and Check In commands now give status as to what is occurring.

• Refresh Source Control Status. In the VS Enhanced client, there’s a new menu item in the File->Vault submenu to refresh all source control statuses to update file icons in the Solution Explorer.

• 64 bit support. We’ve corrected the installer issue that was preventing server installs on a 64 bit OS. IIS will still need to be put into 32 bit mode.

• Ant Tasks. Tasks are included for calling Vault source control operations from the Ant build tool.

• Java CLC. For users on non-Windows platforms, there is now a Java based command line client.

• New Web Diff Page. The Web Diff page has been rewritten to make it more useful for code reviews.

Post Reply