Fortress 1.1.2 Release Notes

[jeremy_sg]

SourceGear Fortress 1.1.2 is a maintenance release for Fortress 1.1. If you have not upgraded to a 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.
Major Changes:

* New 64-bit server installer. There is now a native 64-bit build of the server.
* IIS7 is now supported without turning on the IIS6 compatibility mode.
* The client install is no longer a component of the server install. At the end of the server installation, you will be prompted to run the client install seperately. The server and the client must be uninstalled independantly as well.
* New Cruise Control.Net plugin. This new plugin offers fewer login/logout requests on the server, as well as performance and accuracy improvements.
* In the stand-alone GUI client, pending a delete for a file no longer deletes the working folder copy automatically. There is a checkbox in the delete dialog to control this behavior.

API

* ServerOperations will now automatically refresh before committing.
* Two dlls needed to create plugins are now included in the ClientAPI.zip file

CC.Net plugin

* Added a new plugin for Cruise Control.Net
* Fewer login events. The plugin will stay logged in between polling events whenever possible for better performance.
* Polling done by checking folder version instead of a history query to enhance performance and accuracy.

CLC

* There is a new -resolvemerge flag for the CLC commit command, which will resolve all Needs Merge files on checkin.
* Checkout with wildcard is now working again.
* There is now a -backup option for undocheckout.
* The CLC now lists files and folders when -norecursive is supplied to LISTFOLDERS
* There is now a flag to force subfolders to use the inherited working folder for setworkingfolder and unsetworkingfolder

Client

* Files weren't being displayed as Checked out, if the Check Outs column was not shown
* Fixed some startup errors that occurred when complicated namespace changes were pended
* Pending a delete for a file no longer deletes the working folder copy automatically. There is a checkbox in the delete dialog to control this behavior.
* Deleted files that were modified are now placed in _sgbak (in your working folder) rather than in a cache folder, so they're easier to recover.
* There's an option (in Local Files pane) to set the default behavior.
* The checkbox in the delete confirmation allows you to change that default case-by-case.

DiffMerge

* Added the ability to switch between vertical and horizontal panel layout in File Diff and File Merge windows. Previously, file panels in these windows were shown side-by-side with a vertical splitter between them. This is useful when your files have long lines and you can't see the entire line without horizontally scrolling.
* Added External Tool feature. DiffMerge can now be configured to invoke an external, third-party tool for various types of files (based upon the file suffixes). This allows you, for example, to select special tools for XML or Word documents.
* Added alternate cut/copy/paste keyboard shortcuts for Windows and Linux versions. We now support Ctrl+Insert, Shift+Insert, and Shift+Delete.
* Added "files are different/same" information to the "binary files cannot be loaded" dialog by doing a raw comparison of the files.

Folder Export/Import

* Folder Export/Import bug fix for move/rename and Edit of a file in the same transaction
* Folder Export/Import bug fix for items that had been shared from history.

Work Item Tracking changes

* Better scaling for GUI bug tracking form
* CC.Net plugin has a buildpublisher which allows for updating of Fortress Items referenced by the build with a comment including the build label or folder version.
* Sorting by custom field was causing an error
* Sorting by Milestone was inconsistent where two milestones had the same due date.

Power Toys

* The new Command line deploy power toy is now released.

Server

* Host headers were causing problems in some Admin web pages
* Undo checkout from different machine generated a FailDBFault exception.
* The logic for the "Request database deltas on repository cache miss" was reversed, resulting in long startup times in some cases.
* Weekly log file backups were broken.

Server Installer Changes

* New 64-bit server installer. There is now a native 64-bit build of the server.
* IIS7 is now supported without turning on the IIS6 compatibility mode.
* The client install is no longer a component of the server install. At the end of the server installation, you will be prompted to run the client install seperately. The server and the client must be uninstalled independantly as well.
* Occasional upgrades failing due to "Vault is in single-user mode" error message (fixed)

VSIP

* The Perform Repository Deletions setting is now respected in the VSIP client
* Web site projects were pending adds for empty bin folders
* Many Checkout performance improvements in the VSIP client
* Adding a web reference to a web application project hung at Ending Transaction
* Performance improvements when right-clicking large projects.
* Major performance improvements related to refreshing status glyphs.

Client/Server Version Compatibility:

It is always recommended that your client and server versions match exactly (e.g., a 1.1.2 client should be connecting to a 1.1.2 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.