Release Notes for Vault 4.1.2

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

Moderator: SourceGear


Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
PostPosted: Thu May 29, 2008 3:28 pm
SourceGear Vault 4.1.2 is a maintenance release for Vault 4.1. If you have not upgraded to Vault 4.1 version, see http://www.sourcegear.com/vault/releases/4.1.html for more information.

Installation Notes

• This upgrade includes an update to an index on the labels database table. This update may take a long time while installing.

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

• 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.
Major Changes:

* New 64-bit server installer. There is now a native 64-bit build of the server.
* IIS7 is now supported without turning on the IIS6 compatibility mode.
* The client install is no longer a component of the server install. At the end of the server installation, you will be prompted to run the client install seperately. The server and the client must be uninstalled independantly as well.
* New Cruise Control.Net plugin. This new plugin offers fewer login/logout requests on the server, as well as performance and accuracy improvements.
* In the stand-alone GUI client, pending a delete for a file no longer deletes the working folder copy automatically. There is a checkbox in the delete dialog to control this behavior.

API

* ServerOperations will now automatically refresh before committing.
* Two dlls needed to create plugins are now included in the ClientAPI.zip file

CC.Net plugin

* Added a new plugin for Cruise Control.Net
* Fewer login events. The plugin will stay logged in between polling events whenever possible for better performance.
* Polling done by checking folder version instead of a history query to enhance performance and accuracy.

CLC

* There is a new -resolvemerge flag for the CLC commit command, which will resolve all Needs Merge files on checkin.
* Checkout with wildcard is now working again.
* There is now a -backup option for undocheckout.
* The CLC now lists files and folders when -norecursive is supplied to LISTFOLDERS
* There is now a flag to force subfolders to use the inherited working folder for setworkingfolder and unsetworkingfolder

Client

* Files weren't being displayed as Checked out, if the Check Outs column was not shown
* Fixed some startup errors that occurred when complicated namespace changes were pended
* Pending a delete for a file no longer deletes the working folder copy automatically. There is a checkbox in the delete dialog to control this behavior.
* Deleted files that were modified are now placed in _sgbak (in your working folder) rather than in a cache folder, so they're easier to recover.
* There's an option (in Local Files pane) to set the default behavior.
* The checkbox in the delete confirmation allows you to change that default case-by-case.

DiffMerge

* Added the ability to switch between vertical and horizontal panel layout in File Diff and File Merge windows. Previously, file panels in these windows were shown side-by-side with a vertical splitter between them. This is useful when your files have long lines and you can't see the entire line without horizontally scrolling.
* Added External Tool feature. DiffMerge can now be configured to invoke an external, third-party tool for various types of files (based upon the file suffixes). This allows you, for example, to select special tools for XML or Word documents.
* Added alternate cut/copy/paste keyboard shortcuts for Windows and Linux versions. We now support Ctrl+Insert, Shift+Insert, and Shift+Delete.
* Added "files are different/same" information to the "binary files cannot be loaded" dialog by doing a raw comparison of the files.

Folder Export/Import

* Folder Export/Import bug fix for move/rename and Edit of a file in the same transaction
* Folder Export/Import bug fix for items that had been shared from history.

Power Toys
* The new Command line deploy power toy is now released.

Server

* Host headers were causing problems in some Admin web pages
* Undo checkout from different machine generated a FailDBFault exception.
* The logic for the "Request database deltas on repository cache miss" was reversed, resulting in long startup times in some cases.
* Weekly log file backups were broken.

Server Installer Changes

* New 64-bit server installer. There is now a native 64-bit build of the server.
* IIS7 is now supported without turning on the IIS6 compatibility mode.
* The client install is no longer a component of the server install. At the end of the server installation, you will be prompted to run the client install seperately. The server and the client must be uninstalled independantly as well.
* Occasional upgrades failing due to "Vault is in single-user mode" error message (fixed)

VSIP

* The Perform Repository Deletions setting is now respected in the VSIP client
* Web site projects were pending adds for empty bin folders
* Many Checkout performance improvements in the VSIP client
* Adding a web reference to a web application project hung at Ending Transaction
* Performance improvements when right-clicking large projects.
* Major performance improvements related to refreshing status glyphs.

Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 4.1.2 client should be connecting to a 4.1.2 server). 4.1.x clients are able to communicate with any 4.1.x server, but specific bug fixes will not work correctly if they required both client and server changes. 4.1.x clients and servers are not compatible with 1.x, 2.x, or 3.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.
Subscribe to the Fortress/Vault blog

Return to Knowledge Base (Vault)

Who is online

Users browsing this forum: No registered users and 4 guests