If installing this version of the VssConnect server does not fix the problem, please contact VssConnect support contact@vssconnect.com
A checkbox has been added to the 'advanced' page of the VssConnect admin to enable/disable debug logging.
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.
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.
This uncommon problem has not been fixed, but the effects of the bug have been mitigated so that local file changes are not lost.
This exception will occur if VSS changes the file during checkin due to keyword expansion and the file is large.
'Rename' records in the project history now show the item's file name in the 'Item' column.
Pinned and Unpinned items in the project history now show the name of the file in the 'Item' column.
The file history now shows a distinction between project labels and individual file labels.
This issue only affects VssConnect servers with VSS6 installed on them and only affects multiple checkouts of a file to the same user.
The 'About' page in the Server Admin program now has a button that opens the server log file folder.
The server now create a log file which can be used for debugging server issues.
Sharing\moving a file into a project that already contains the file no longer generates an error.
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.
Under the right conditions, the VssConnect server may fetch a copy of files being shared/moved to the local drive of the server.
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.
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.
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.
The VssConnect server service no longer needs to run under an account that needs to be able to write to HKEY_LOCAL_MACHINE.
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.
Fixed a bug which caused a trial license issued on the last day of the month to be invalid.
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.
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.
Label comments now appear in the project/file 'Comment' column of the file/project history window.
Moving a file to a solution folder that does not exist in the Source Safe database no longer throws an unhandled exception.
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.
VssConnect now sets the correct date when getting labeled projects (previously VssConnect would set the files dates to the current date/time).
Clicking OK on named database dialog clears modified flag even though changes have not been saved yet.
VssConnect no longer throws a missing method exception when getting a labeled project when using VSS 6 on the VssConnect server machine.
Fixed .NET 1.1 framework detection when installing on Windows Vista.
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.
VssConnect now supports the ability to set the file encoding when adding files.
Fixed an exception in that occurs when sharing and branching (copying) a project from one location to another.
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.
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.
This update is required to correctly display project histories in the latest VssConnect client.
The VssConnect server admin program now shows a list of currently connected users.
VssConnect now interrupts a project branch when the command is cancelled.
Implemented a work around for a .NET remoting bug that caused licenses to be consumed even after the client was no longer connected.
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.
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.
VssConnect server now indicates when a connection is rejected because the trial license has expired.
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.
The VssConnect server configuration wizard has been improved. It now provides better descriptive information particularly with reference to authentication and service account information.
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.
Project deployment command can now be disabled on the VssConnect server (it is disabled by default).
VssConnect now checks user permissions when deploying project to the server. NOTE: This only works if VssConnect server is configured to 'Enable OS Authentication'.
The license list in the server admin application now contains a column showing the user how many client licenses each key supports.
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.
The VssConnect server install now checks to make sure Visual SourceSafe 6 or greater is installed before proceeding.
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.