3.0.3 Release Notes

[dan]

The following features and changes have been included in the 3.0.3 release:

<b>IDE Client</b>
· Opening a project containing a folder that was deleted in the repository no longer gives “Access Error”

<b>Diff/Merge Tool</b>
· Selecting extremely large amounts of text for copying no longer causes exception.

<b>Windows GUI</b>
· Mitigated “process cannot access the file” error that would occassionally happen on small class of machines.

<b>Admin Tool</b>
· Mergable file list can now be overriden if multiple repositories have different values.

<b>Command Line Client</b>
· Getting a file label from its parent folder now retrieves the version at that label, rather than the currrent version of the file.

<b>Server</b>
· Improved usage of RAM consumed by server by using a custom serializer and also by not caching unnecessary tree deltas.
· Shadow Folders can now be configured to store their state data in a folder that the Vault Service has access to
· Shadow Folders now correctly respect impersonation settings in the web.config file.
· Active Directory Authentication is now enabled when server is not on the same domain that is being checked.
· Optimized Checkout List computation when folder security is on.

<b>Server Installer</b>
· Installer now writes out correct user name to web.config file when using both impersonation and SQL authentication.




<b>Client/Server Version Compatibility</b>
It is always recommended that your client and server versions match exactly (e.g., a 3.0.1 client should be connecting to a 3.0.1 server). 3.0.x clients are able to communicate with any 3.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 3.0.x clients and servers are <b>not</b> compatible with 1.x or 2.x clients and servers.

<b>Upgrading From Previous Versions</b>
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.