Vault Standard Release Notes
This release is a major upgrade, and you must purchase new licenses for all of your users. For pricing details, see the Vault pricing page. Once a Vault database has been upgraded to 6.0, it cannot be used with previous versions. If you install 6.0 over an existing database, you must enter new license keys to use the system.
Please ensure you have a verified backup of all your Vault related databases before upgrading, and upgrade at a time when it is convenient to not have access to the server.
Vault 6.0 is not backwards compatible with previous versions of Vault. In essence, Vault 6.0 clients will only interact with Vault 6.0 servers and vice versa. Vault 2.x, 3.x, 4.x, and 5.x clients and servers are not compatible with Vault 6.0 clients and servers.
For details on Vault licensing, including upgrade policies and demo keys, please see the Licensing FAQ.
Known Issues:
Vault Standard 6.0 and Eclipse integration has not yet been implemented. This will be fixed in Vault 6.0.1. In the meantime you can use the Vault GUI Client for source control operations while doing your development in Eclipse.
What's New Since Vault 5.1.2:
The Vault Server now requires .NET Framework 4 (Full installation).
Added support for the following system configurations/components:
- Microsoft Windows 8
- Microsoft Windows Server 2012
- Microsoft SQL Server 2012 (database backend)
- Microsoft Visual Studio 2010 (SP1) and Microsoft Visual Studio 2012
- Microsoft SQL Server Management Studio 2005 and higher
Due to incompatibilities with .NET 2.0, Vault integration in Visual Studio .NET (2002) and Visual Studio .NET 2003 is no longer functional. The Vault GUI client or Vault CLC can still be used for source code operations for your project.
For the full listing of supported IDEs please see the Vault Compatibility Chart.
Vault Server
The Vault Server will run on Microsoft Windows Operating Systems configured for the United States Federal Information Processing Standard (FIPS).
Server contains a Find in Files Index server used for parsing changes made to repository files.
Server contains a Notification server used to record and send events to Vault users.
Vault Notification Server sends out standard email as well as email digests.
Added notification events for deleted work items and deleted work item comments.
Addressed an issue where a client that disconnects while downloading a large number of files would cause the Vault server to log the message “Error downloading file! The remote host closed the connection”. This caused instability for subsequent Vault Server connections.
Changed behavior of Admin Tool's Undo Checkout to allow pagination as a software update from Microsoft Security Bulletin MS11-100 disallowed the web page to operate with a large number of checked out files.
Vault Server Installation
Creates different Application Pools within IIS 7.0/7.5 to optimize use of system resources across multiple web services.
Fixed installer to allow XML/HTML special characters ('<', '>', '&', etc.) for Vault Administrator password and Custom .NET identity.
Addressed problem when using a “Custom .NET account” to install to SQL Server with Windows authentication.
Vault Client
The Vault client will run on Microsoft Windows Operating Systems configured for the United States Federal Information Processing Standard (FIPS).
Added Find in Files to search for text phrases within a file, group of files, or a folder (and its sub folder items).
Receive application notifications for source control events.
Added an option to suppress notifications for self generated source control events.
Fixed issue where the client was saving more versions than what was specified in the option to limit the number of baseline files.
Addressed problem where an automatic merge from a GET or from within Merge Branches would add an extra newline character into the resulting file.
Added Ctrl+F for diffing from within History Explorer .
Added the “Merge Markers” feature to track merges from source to destination folders within Merge Branches.
Merge Branches has optimized history retrieval to retrieve data by a date range or certain number of days.
On Folder Properties, the list of deleted items are now sorted by deletion date. And the list is also sortable.
On Folder Properties, the list of deleted items correctly identifies files deleted in a branch or snapshot as files.
Command Line Client
Added new history options for -includeusers as well as -includeactions
Added functionality to search for text within the repository using the FINDINFILES or FINDINFOLDERS commands.
Vault Classic Client
Vault Classic Client can be configured to run on a multitude of .NET Framework versions. The Vault Classic client requires a minimum of .NET 2.0 Framework, but can now run on Windows 7 or Windows 8 as well as Visual Basic 6 or Visual Studio 6.
Fixed problem where the Vault Classic Client would not generate a log file.
Added support for integration with SQL Server Management Studio 2005/2008.
Vault Visual Studio Enhanced Client
Added support for Visual Studio 2010 (SP1) / Visual Studio 2012.
When excluding a file from a project, the Visual Studio Enhanced Client now prompts if the file should also be deleted from Vault.
Added capability to see notifications events for source control events.
The Vault Visual Studio Enhanced client allows the DIFF command regardless of the file's status.
Messages within Vault output Tool Pane now display a timestamp.
Fixed issue where deleting a file from a web site project would not remove the item from Vault source control.
Addressed inconsistencies with source control commands for related files. For example, a change to a form in Visual Studio's Designer would not checkout both the source, designer, and resource files, or checking out the .filters file when the corresponding .vcxproj file is checked out.
Corrected behavior for handling linked files within a solution.
Fixed issue allowing an overwrite of a read-only file.
Vault Shadow Folder
Fixed problem with Vault Shadow Folder where deleted files within a change set were not deleted in a shadowed folder.
Addressed a problem within Vault Shadow Folder when a shared file is deleted from Vault Source Control, the shared file would sometimes be deleted from the incorrect location in the shadowed folder.
For new installations, the default Shadow Folder cache path has been relocated to avoid permissions issue.
CC.NET Integration
Corrected issue where a login failure would require a CC.Net restart. Now, when a login failure occurs with the Vault 6.0 CCNet plugin, the login will re-attempt on subsequent CC.Net query cycles.
When the option for deleteItemsThatAreNotInTheRepository is used, the client will delete only those items rather than delete the entire folder from disk and re-download all files.
Vault Folder Export/Import
Added Export option to not export labels.
Added Import option to ignore label errors.
Client/Server Version Compatibility
It is always recommended that your client and server versions match exactly (e.g., a 6.0 Vault Professional client should be connecting to a 6.0 Professional server). 6.0.x clients are able to communicate with any 6.0.x server within the same edition, but specific bug fixes may not work correctly if they required both client and server changes.
Previous versions of Vault clients and servers are not compatible with 6.0 clients and servers. Vault Professional clients and servers are not compaitible with Vault Standard clients and servers.
Upgrading From Previous Versions
It is recommended that you backup your Vault databases prior to an upgrade. This can be done from either the Web Admin tool, or SQL Server Enterprise Management Studio.
To upgrade from a previous installation of Vault, simply invoke the new installer, and choose the same options that were selected when it was previously installed. Program files and configuration settings should be automatically updated to reflect the upgrade. Note that the server installation will not delete your databases unless you explicitly tell it to.
You may also safely uninstall Vault first, and then install Vault 6.0. As with the Vault Server installation, an uninstall will not delete your database unless you explicitly tell it to.