Release Notes for Vault 4.1.3

[jeremy_sg]

SourceGear Vault 4.1.3

SourceGear Vault 4.1.3 is a maintenance release for Vault 4.1. If you have not upgraded to Vault 4.1 version, see http://sourcegear.com/vault/releases/4.1.html for more information.
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.

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

* Branch performance has been dramatically increased
* Fixed a server memory corruption when rolling back a shared and renamed file
* Fixed a server memory corruption when running under the 2.0 framework
* 4.1.3 will now work for SQL Server 2008

API

* Added comment filtering to versionhistory and history in ServerOperations

Classic Client

* Fixed an error that occurred when dealing with subordinate files (like .designer.cs) in Visual Studio 2008

Cruise Control.Net

* Rememberlogin is now supported in the new cc.net plugin
* Non-standard port numbers are now supported
* Fixed a common source of a GetLatestVersionFailedException
* The useWorkingDirectory parameter is now supported
* Blank passwords will now be accepted
* The _sgbak backups will no longer be created
* Build publisher was adding bug reference comments twice (Fortress only)

Dreamweaver

* Dreamweaver CS3 will no longer crash when changing sites

Eclipse

* Fixed a null pointer exception that sometimes occurred when trying to add a project
* A case-sensitive filtering problem caused the pending changes view to be blank
* A share operation in Eclipse when there are Deletes pending would fail

GUI

* There is now a registry setting to configure the client side upload timeout
* Options: The "Limit number of backup files" text box is only enabled only when the checkbox is checked
* File list wasn't refreshing properly
* OverrideNativeEOL conflicted with Unknown file resolution to cause FailDeltaApply or FailFileInvalidChecksum on checkin
* Failed check out removes read-only flag for a file

History Explorer

* A saved History Query for past X days would continue to expand in scope over time

Install

* The installer now does some extra checks to see if VS2008 or VS2005 is actually installed
* 4.1.3 will now work for SQL Server 2008

Merge Branches

* Duplicate files were sometimes added during a merge branches operation

NAnt

* ResolveMerge now works correctly

Power Toy

* DeployWizard: exported xml is formatted for readability
* Deploy Command Line: The -server command line parameter is now respected

Server

* When branching an object, you may now choose to keep the source object's modification time
* When two users had an email watcher set for the same folder, only one user received an email update
* The Open Items for All Projects page showed inactive projects
* Fixed a server memory corruption when rolling back a shared and renamed file
* Branch performance has been dramatically increased
* Fixed a server memory corruption when running under the 2.0 framework

Shadow Folders

* Shadow folder crash "Path is not of legal form" when using a custom cachepath
* Shadow Folder modification time was not working correctly

Source Control Ops

* Fixed a few null reference exceptions or "you have no rights to any items in this repository" errors on startup, related to pending changes
* Fixed a null reference error when a working folder had no baselines present

VSIP

* Adds for setup projects weren't being pended
* Fixed an intellisense failure after reloading solution
* Open From Vault appeared to never finish if a project can't be loaded
* We now prompt to check out Renegade files when returning online in VSS mode
* Fixed a Visual Studio 2008 glitch when checking out a file that's open, the lock icon on the file's tab wouldn't go away until you reopen it
* Going online via the menu command now remembers the online setting
* The Needs Merge warning dialog is now displayes when checking in
* Sped up pending a file add in large solutions

VSS Import

* VSS Import now runs on 64-bit Windows

Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 4.1.3 client should be connecting to a 4.1.3 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.