SourceGear Vault 4.0.1 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.

The following changes are included in this release:

Visual Studio 2005 Client Only

• Files and folders directly in the solution were causing failures from failing to load/bind a solution to "Project node count mismatch".
  
• Projects with web references were crashing Visual Studio when right-clicked.
  
• Line history was crashing Visual Studio in some cases.
  
• Web Site projects bound to an HTTP server were failing.
  
• Binding a new project would fail if "Save new projects when created" was unchecked. With 4.0.1, all projects must be saved to disk before allowing a bind command.
  
• There are now instructions for converting solutions and projects from the Visual Studio 2003 compatible client to the Visual Studio 2005 client. Please review them at: http://support.sourcegear.com/viewtopic.php?t=7937
  

General Client issues:

• Fixed "VaultPkg.dll failed to register" error message on installation.
  
• The Visual Studio 2003 Compatible Client was unable to find the Diff/Merge application.
  
• Fixed FogBugz integration.

Server Issues:

• Users were reporting getting 404 errors due to the web.config file failing to upgrade.
  
• A shortcut to the new Admin Web client is now included in the Start Menu for the server machine.
  
• Obliterate was failing when custom identity impersonation was used.
  
• The installer now launches a web page to the correct URL when IIS is not configured to listen to http://localhost

Client/Server Version Compatibility

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