The following changes are included in this release:
Client Only
- Fixed problem where Date / Time are sent in incorrect format across time zones when using a different version of .Net Framework than the Server. For example, Vault Client with .Net Framework 1.1 connecting to Vault Server with .Net Framework 2.0.
- Fixed client to correctly handle Prompt for overwrite dialog.
- Import removed unnecessary tree updates during import.
- Import now imports correctly for large imports by temporarily disabling auto-refresh in the Export Import Tool.
It is always recommended that your client and server versions match exactly (e.g., a 3.5.1 client should be connecting to a 3.5.1 server). 3.5.x clients are able to communicate with any 3.5.x server, but specific bug fixes will not work correctly if they required both client and server changes. 3.5.x clients and servers are not compatible with 1.x, 2.x, 3.0.x, or 3.1.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
Important: If you are upgrading from a pre 3.1 version of Vault, the server installation will take longer than normal because the database needs to be converted to a new format.
Also, the client install will upgrade client cache files to a new format if you are currently on a pre 3.1 release. This will not affect upgrade times, but also will not allow you to revert back to a pre 3.1 client without losing client state information.