Release Notes - VssConnect: 1.6.3639 Server

1563: Bug: 'SourceSafe was unable to finish writing a file.  Check your available disk space, and ask the administrator to analyze...'

If installing this version of the VssConnect server does not fix the problem, please contact VssConnect support contact@vssconnect.com

1498: Improvement: Checkbox added to server manager to enable/disable debug logging.

A checkbox has been added to the 'advanced' page of the VssConnect admin to enable/disable debug logging.

Release Notes - VssConnect: 1.6.3577 Server

1487: Bug: Checkin may fail if 'keep checked' option was used previously.

Users may run into this bug if VSS2005 is installed on the VssConnect server machine and 'multiple checkouts' is NOT enabled for the VSS database. If a file is checked out, then checked in with the 'keep checked out' option checked, the next time the file is checked in, the checkin will fail and file changes may be lost. The user must then undo the checkout in order to check the file in.

Release Notes - VssConnect: 1.6.3567 Server

1473: Bug: VssConnect server can no longer be installed on Windows 2000

The VssConnect server can be installed on Windows 2000 but it will default to running under the Local System account instead of the more secure 'Local Service' account which is not available on Windows 2000.

1468: Bug: During the check in process, VssConnect sends back a 'merged' version of the file and the check in fails

This uncommon problem has not been fixed, but the effects of the bug have been mitigated so that local file changes are not lost.

1467: Bug: VssConnect Server may generate a 'locked file exception' during check in

This exception will occur if VSS changes the file during checkin due to keyword expansion and the file is large.

1463: Bug: 'Rename' project history records do not show file name in the item column.

'Rename' records in the project history now show the item's file name in the 'Item' column.

1462: Bug: Pinned and Unpinned project history records do not show file name in Item column

Pinned and Unpinned items in the project history now show the name of the file in the 'Item' column.

1459: Bug: File history list does not show distinction between a direct file label and an indirect project label

The file history now shows a distinction between project labels and individual file labels.

Release Notes - VssConnect: 1.6.3557 Server

1455: Bug: VssConnect may operate on wrong checkout record when a user has a file checked out to more than one location.

This issue only affects VssConnect servers with VSS6 installed on them and only affects multiple checkouts of a file to the same user.

Release Notes - VssConnect: 1.6.3536 Server

1439: Improvement: Added Button to Server Admin to Locate the Server Log File

The 'About' page in the Server Admin program now has a button that opens the server log file folder.

1438: Improvement: Added Server Logging

The server now create a log file which can be used for debugging server issues.

1401: Improvement: Sharing\moving a file into a project that already contains the file no longer generates an error.

Sharing\moving a file into a project that already contains the file no longer generates an error.

1371: Improvement: VssConnect Should Warn the User When a File is Already Checked Out.

VssConnect now does a better job of checking if a file is already checked out by another user and alerting the user if it is. Note: VssConnect Client 1.3.3528 or greater is required in order for this improvement to work.

1402: Bug: Sharing/moving files can cause the files to be fetched to the local drive of the VssConnect server.

Under the right conditions, the VssConnect server may fetch a copy of files being shared/moved to the local drive of the server.

Release Notes - VssConnect: 1.6.3388 Server

1319: Improvement: 'Shared' Actions in Project History Now Show File Name in Item Column

1288: Improvement: VssConnect service can now run under the 'Local Service' account.

The VssConnect server service can now run under the 'Local Service' account when using VSS2005 and impersonation. The built in 'Local Service' account has limited rights and provides greater protection in the event of a VssConnect server security breach.

1135: Improvement: Operations on large files can cause the VssConnect server to become unresponsive.

Due to SourceSafe COM API restrictions, operations on large files can cause the VssConnect server to become unresponsive until the operation is complete. Operations on large files are now delegated to a separate process allowing the server to continue servicing requests.

1107: Improvement: Server temp path has changed to allow VssConnect to run under a limited user account.

The path of the temp folder used by the VssConnect server has changed to allow the VssConnect server service to run under a limited user account.

1105: Improvement: VssConnect service no longer needs to run under an account that can modify HKEY_LOCAL_MACHINE

The VssConnect server service no longer needs to run under an account that needs to be able to write to HKEY_LOCAL_MACHINE.

1237: Bug Fix: Local file version number is not correct after undoing a checkout (multiple checkouts only).

If a user checks out version X of a file and the file is subsequently updated to version X+1 by another user, undoing the checkout will correctly fetch version X but the file properties dialog will report the version of the local file as being version X+1 i.e. the latest version.

1133: Bug Fix: Trial license issued on the last day of the month does not work.

Fixed a bug which caused a trial license issued on the last day of the month to be invalid.

Release Notes - VssConnect: 1.6.3094 Server

957: Improved Support VS.NET 2005 and VS.NET 2008

Improved VS.NET support to allow VS.NET to query for file status and to determine if files have been added or deleted from a project.

Release Notes - VssConnect: 1.6.2892 Server

837: Fix: Recovering a File May Place a Copy of the File in the System32 Folder

Under certain conditions, recovering a file would cause a copy of the file to be placed in the VssConnect server's System32 folder. The conditions seem to be as follows:

The user has no working folders assigned in SourceSafe on the VssConnect server machine and the SourceSafe database is local to the VssConnect server.

This appears to be a bug in the SourceSafe COM API and a workaround has been implemented in the server code to prevent this from happening.

Release Notes - VssConnect: 1.6.2832 Server

719: Improvement: Label Comments Can Now Be Viewed In Project History

Label comments now appear in the project/file 'Comment' column of the file/project history window.

742: Fix: Moving Files to Sub-folders In Visual Studio 2005

Moving a file to a solution folder that does not exist in the Source Safe database no longer throws an unhandled exception.

725: Improvement: VssConnect Creates VsscCheckouts Folder On Server Only When Required

VssConnect now creates VsscCheckouts folder in Source Safe database folder only when a file is checked in that requires use of this folder (since the checkout path is too long). This only applies to VssConnect when the VssConnect server is using VSS 6.0.

720: Fix: Getting Files From a Project Label Now Sets File Date Correctly

VssConnect now sets the correct date when getting labeled projects (previously VssConnect would set the files dates to the current date/time).

Release Notes - VssConnect: 1.6.2769 Server

693: Fix: Clicking OK on Named Database Dialog Clears Modified Flag

Clicking OK on named database dialog clears modified flag even though changes have not been saved yet.

689: Fix: Getting Labeled Project Throws 'Missing Method' Exception

VssConnect no longer throws a missing method exception when getting a labeled project when using VSS 6 on the VssConnect server machine.

Release Notes - VssConnect: 1.6.2705 Server

Fix: .NET Framework V1.1 Detection on Vista

Fixed .NET 1.1 framework detection when installing on Windows Vista.

Release Notes - VssConnect: 1.6.2704 Server

616: Improvement: Prompt User to Install .NET 1.1

VssConnect now requires .NET 1.1 to be installed on the server machine. Previously, having .NET 2.0 alone was allowable but it has since been determined that problems can occur when the VssConnect server loads .NET 2.0 instead of .NET 1.1.

Release Notes - VssConnect: 1.6.2681 Server

593: Feature: Setting Encoding When Adding Files

VssConnect now supports the ability to set the file encoding when adding files.

Release Notes - VssConnect: 1.6.2647 Server

561: Fix: Exception When Sharing and Branching a Project

Fixed an exception in that occurs when sharing and branching (copying) a project from one location to another.

Release Notes - VssConnect: 1.6.2625 Server

491: Improvement: Added Information For Label Exception

If an exception is raised while labeling an item, the exception now contains the item path, label and comment. This will improve future versions of VssConnect.

512: Improvement: Temp Folder Check On Login

The VssConnect server now checks that the user logging in can create temp files and folders on the server machine. This will make troubleshooting permissions problems easier.

526: Improvement: Support For New Project History Grid

This update is required to correctly display project histories in the latest VssConnect client.

Release Notes - VssConnect: 1.6.2597 Server

6: Improvement: Connected User List

The VssConnect server admin program now shows a list of currently connected users.

486: Improvement: Cancel When Branching Project

VssConnect now interrupts a project branch when the command is cancelled.

483: Fix: License Counting

Implemented a work around for a .NET remoting bug that caused licenses to be consumed even after the client was no longer connected.

424: Improvement: Splash Screen for VssConnect Admin

Added a small splash screen to the VssConnect Server Admin program to indicate that the program has started. This may be useful when the event log has a large number of entries which can slow down the start-up of the application.

Release Notes - VssConnect: 1.6.2536 Server

410: Improvement: Running VssConnect In Windows Vista

The VssConnect server admin program must now be run as an administrator in Windows Vista. This allows the VssConnect service to be controlled and allows the user to change the server encryption key.

Release Notes - VssConnect: 1.6.2523 Server

371: Improvement: Failed Connection Message

VssConnect server now indicates when a connection is rejected because the trial license has expired.

387: Fix: Problem Updating Local File

This fix takes care of a problem causing VssConnect not to replace the local copy of a file if the current version of the file in SourceSafe is 1 and the local copy of the file is version 1 and has been modified and 'quick get' is enabled.

Release Notes - VssConnect: 1.6 - Server

334: Improvement: VssConnect Server Configuration Wizard

The VssConnect server configuration wizard has been improved. It now provides better descriptive information particularly with reference to authentication and service account information.

94: Improvement: Username/Password Management

When Visual Studio 2005 is installed on the VssConnect server machine, server administration is simplified. The VssConnect server now impersonates the connected user, which allows the user's domain password to be different from their Source Safe password. In addition, the VssConnect server can now run under an account that does not have permission to access the Source Safe database.

61: Feature: Project Deployment

Project deployment command can now be disabled on the VssConnect server (it is disabled by default).

60: Improvement: Project Deployment Command

VssConnect now checks user permissions when deploying project to the server. NOTE: This only works if VssConnect server is configured to 'Enable OS Authentication'.

117: Feature: License Count in Server Admin

The license list in the server admin application now contains a column showing the user how many client licenses each key supports.

174: Bug: Version Column After Check In

Fixed a bug caused by a change in Source Safe 2005. Version column should now be correct following a file check in to a multiple check out database when using VSS 2005 on the VssConnect server.

143: Feature: Install Checks for Suitable Version of SourceSafe

The VssConnect server install now checks to make sure Visual SourceSafe 6 or greater is installed before proceeding.

140: Feature: Server Admin Startup Time

The server control program startup time has been improved. This is particularly apparent when the application event log on the server machine has a lot of entries in it.

Produced by FogBugz