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.