SourceGear Vault 4.0.3 is a maintenance release for Vault 4.0. If you have not upgraded to Vault 4.0 version, see
http://www.sourcegear.com/vault/releases/4.0.html for more information.

Known issues:

There are still issues which prevent using projects in the Visual Studio 2005 IDE Client which are bound to source control in a solution which is not bound. If you use this configuration, please remain on the 2003 compatible client until these issues have been resolved.

There is now an automated tool to convert projects and solutions bound to the Visual Studio 2003 compatible client to the new Visual Studio 2005 client. You can download that tool from:
http://support.sourcegear.com/viewtopic.php?t=8214

If you wish to convert your solutions and projects manually, follow the steps outlined at:
http://support.sourcegear.com/viewtopic.php?t=7937

The following changes are included in this release:

Visual Studio 2005 Client Only

• Visual Studio will no longer prompt to reload files after a checkin which didn't modify the contents of the files.
  
• Solution folders containing unloaded projects caused "Specified cast is not valid." error.
  
• Removed misleading controls from the Get Latest dialog
  
• Some projects were giving "Unable to determine repository path" when trying to go Online
  
• The VS 2005 client is no longer auto-committing manually added items
  
• There were casting errors on some Add to Vault operations
  
• Some commands were enabled when a project was offline that should have been disabled.
  
• The VS 2005 client was not working with authenticating proxies.

General Client issues:

• There were performance concerns when there were move/rename/delete operations pended.
  
• The Eclipse IDE client was not updating FogBUGZ cases correctly on checkin.
  
• The Dreamweaver client was not appearing in the options for Dreamweaver 8. Please note that Dreamweaver 9 is not yet supported.
  
• The REMEMBERLOGIN command in the command line client was not correctly remebering the login information.

Server Issues:

• The Server install was not setting database permissions correctly on fresh installs using SQL Server authentication.

Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 4.0.3 client should be connecting to a 4.0.3 server). 4.0.x clients are able to communicate with any 4.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 4.0.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.

Miscellaneous

Also, the client install will upgrade client cache files to a new format if you are currently on a pre 4.0 release. This will not affect upgrade times, but also will not allow you to revert back to a pre 4.0 client without losing client state information.