Release notes for 2.0.0

A collection of information about Fortress, including solutions to common problems.

Moderator: SourceGear

Post Reply
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear

Release notes for 2.0.0

Post by jeremy_sg » Wed Jul 29, 2009 3:48 pm

Fortress 2.0

This release is a major upgrade, and you must purchase new licenses for all of your users. For pricing details, see For licensing FAQs, see: Once a Fortress database has been upgraded to 2.0, it cannot be used with previous versions any more. If you install 2.0 over an existing database, you must enter new license keys to continue working.

Please ensure you have a verified backup of your database before upgrading, and upgrade at a time when it is convenient to not have access to the server. On very large Fortress installations, the upgrade may take several hours.

Fortress 2.0 is not backwards compatible with previous versions of Fortress. In essence, Fortress 2.0 clients will only interact with Fortress 2.0 servers and vice versa. Fortress 1.x clients and servers are not compatible with Fortress 2.0 clients and servers.

Installation notes:

If you are converting a Vault or Dragnet installation, you must uninstall those products before installing Fortress. When uninstalling, choose to keep the databases.

In order to convert an installation of Vault and Dragnet to a Fortress installation, both the sgvault and sgdragnet databases must be on the same SQL server instance. Use the detach and reattach functions in SQL server to move databases if necessary. It is recommended that you convert to the latest version of Dragnet before converting to Fortress.

For users converting from an installation of Vault only, the Fortress work item tracking database will be created automatically.

It is not recommended to convert an installation with only Dragnet. Install Vault 3.5.2 beside your Dragnet installation and convert them as normal.

Known issues:

Important note when upgrading from a 1.0.x release: There is an issue with the upgrade process from the initial Fortress 1.0.x releases which will prevent an upgrade to 2.0 from succeeding. To work around this issue, please uninstall the Fortress 1.0 Server (choosing to keep your databases) before installing Fortress 2.0. Fortress 1.1.x releases are not affected by this issue.

If you've already tried the upgrade and encountered the problem, running the upgrade a second time should work.

Important note when upgrading from the 1.0.6 release. There was a bug in the uninstall routine for the 1.0.6 for users who installed the server and the client together using the server's installer. Upgrading in that situation will succeed, but leave two client shortcuts on the desktop. Please follow the instructions at for instructions on removing the 1.0.6 server and client before upgrading.

What's New:
Major Features

Shelve lets you store changes in the server without checking them in. These "shelveset" can be shared among Fortress users, or restored for later checkin. For more information, see: ... helve.html
Web Client Redesign
The Item Tracking Web client has been rewritten to be easier and more powerful. For more information, see: ... e_a_l.html
VSS Handoff
VSS Handoff is a new way to convert from VSS to Fortress. For more information, see: ... urces.html
WebDAV support
The Fortress server now supports WebDav connections, which enables cross-platform support for DreamWeaver.
Visual Studio Checkout Confirmation
The Enhanced Client now has an option to prompt before automatically checking out files.

Other changes:

* Rebind Projects and Solutions - The Fortress server can now automatically rebind Visual Studio projects and solutions to the Visual Studio Enhanced Client.
* Email Settings Improvements - The Email Settings page has a Send Test Email button to verify email settings, and a new field for configuring SSL for the SMTP connection.

* Delete is now available for ghosted files.
* Performance improvements when Ghost folders and files are enabled.

Enhanced Client
* New Tree control for the Commit changes dialog
* Visual Studio 2010 support.

* Disconnect Command - There is a new context menu item to unbind Eclipse projects from the Fortress team provider.
* Passwords can now be remembered
* Check in from a folder in Package Explorer now works correctly

CruiseControl.NET Support
* Reduced memory requirements for users with lots of CC.Net projects, or very large repositories.
Subscribe to the Fortress/Vault blog

Post Reply