SourceGear Fortress 1.1.4 is a maintenance release for Fortress 1.1. If you have not upgraded to Fortress 1.1 version, see http://www.sourcegear.com/fortress/releases/1.1.html for more information.
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.3 beside your Dragnet installation and convert them as normal.
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 1.1 is not backwards compatible with previous versions of Fortress. In essence, Fortress 1.1 clients will only interact with Fortress 1.1 servers and vice versa. 1.0 clients and servers are not compatible with Fortress 1.1 clients and servers.
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 http://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 2008, you will not be able to open solutions that have not yet been upgraded by Visual Studio to the Visual Studio 2008 format.
Server
- Query projects was returning a HTTP 500 error code
- Folder Security Admin Web Client page loaded very slowly for repositories with large trees
- Adding a shadow folder needed to be performed twice if the disk path did not exist
Installer
- An Object Reference exception was being thrown when upgrading 1.1.2 -> 1.1.3 using IIS 7 with compatablity mode turned off
DiffMerge
- The DiffMerge Shell Extension now works on 64bit Vista systems.
Class Client
- Encoding was accidentally changed when EOL conversion was applied
- The Classic client could not add a solution if there was no repository cache file.
Visual Studio Enhanced Client
- Status glyphs were inaccurate in certain project types.
- Files in web site bin folders were being added when they shouldn't be
- The changes made by an implicit get latest/checkout/reload can no longer be undone
- msscci2vsip binding converter now handles projects that aren't beneath the solution on disk. msscci2vsip is now a supported Power Toy
- NodeCounter helps users explore their source control repository to find which folders have the most subitems, as well as which folders have the largest disk space usage. NodeCounter in now a supported Power Toy
- When a project was in the root of a drive, repository paths were not being determined correctly
Command-Line Client
- HTML help is now implemeted for the Java CLC
- CLC GETLABEL fails when an item has been shared two or more times inside the label
- DIFF is now implemented for the Java CLC
Eclipse Plugin
- The Eclipse client was erroneously prompting for file reloads anytime a file was checked in
Client/Server Version Compatibility
It is always recommended that your client and server versions match exactly (e.g., a 1.1.4 client should be connecting to a 1.1.4 server). 1.1.x clients are able to communicate with any 1.1.x server, but specific bug fixes will not work correctly if they required both client and server changes. 1.1.x clients and servers are not compatible with 1.0 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.