SourceGear Fortress 2.0.1 is a maintenance release for Fortress 2.0. If you have not upgraded to Fortress 2.0, see sourcegear.com/fortress/releases/2.0.html for more information.

 

Installation Notes

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.x clients will only interact with Fortress 2.0.x servers and vice versa. Fortress 1.x clients and servers are not compatible with Fortress 2.0 clients and servers.

For details on Fortress licensing, including upgrade policies and demo keys, please see the Licensing FAQ

 

Known issues:

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 support.sourcegear.com/viewtopic.php?t=9653 for instructions on removing the 1.0.6 server and client before upgrading.

When using the VS Enhanced Client's "Open From Fortress" functionality in Visual Studio 2008, you will not be able to open solutions that have not yet been upgraded by Visual Studio to the Visual Studio 2008 format.

 

What's New Since Fortress 2.0:

Client
  • Improved performance when there are large numbers of checked out files
  • Shelve All shelved the incorrect files when items were unchecked in the Shelve dialog
API
  • Improved performance for some API applications
Server
  • Progress wasn't being shown for some repository deletions
  • Some installations could not upload shelved files
  • Removed preferences link from Source Control and Admin web pages
Server Installation
  • Install paths with spaces were failing on IIS 7
  • Connect string was not being set for SQL authentication installations
Visual Studio Enhanced Client
  • Reduced unnecessary refreshes when opening a solution
  • Unshelve was failing when there was an add file inside an add folder
CruiseControl.NET Support
  • Added new option deleteItemsThatAreNotInTheRepository. When this option is turned on, any files or folders which exist in the target working folder, but not in the repository will be deleted. This gives the ability to have a clean build without downloading all of the files.
Item Tracking
  • Categories were not updated when a work item's project was changed

Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 2.0.1 client should be connecting to a 2.0.1 server). 2.0.x clients are able to communicate with any 2.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 2.0.x clients and servers are not compatible with 1.x clients and servers.

 

Upgrading From Previous Versions

It is recommended that you backup your Fortress databases prior to an upgrade. This can be done from either the Fortress Admin tool, or the SQL Enterprise Manager tool.

To upgrade from a previous installation of Fortress, simply invoke the new installer, and choose the same options that were selected when Fortress 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 Fortress first, and then install the upgrade. As with installation, an uninstall will not delete your database unless you explicitly tell it to.