Fortress 1.0.5 Release Notes

Post by **jeremy_sg** » Thu Oct 25, 2007 2:04 pm

SourceGear Fortress 1.0.5 is a maintenance release for Fortress 1.0. If you have not upgraded to Fortress 1.0 version, see http://www.sourcegear.com/fortress/releases/1.0.html for more information.

Known issues:

There is now an automated tool to convert projects and solutions bound to the Visual Studio 2003 compatible client to the new Visual Studio 2005 client. You can download that tool from:
http://support.sourcegear.com/viewtopic.php?t=8214

If you wish to convert your solutions and projects manually, follow the steps outlined at: http://support.sourcegear.com/viewtopic.php?t=7937

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 automatically created.

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.

Changes From Vault 4.0.5:

* Browse for bugs in VSIP client now handles session restart.
* Disabled the ability to set external-user to Active.
* Email notifications were mistakenly garbling a URL that started with http://fortress.domain.com
* API: Added the ability to set the HTML option for bug details and comments.

Client/Server Version Compatibility:

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