Contact
|
FAQ | File Difference |
Getting Started Guide
|
Frequently
Asked Questions |
Q: Why do get the error 'SourceSafe was unable to finish writing a file. Check your available disk space, and ask the administrator to analyze your SourceSafe database.'?
A: If you receive this error, install the latest version of the
VssConnect server. If you continue to receive this error please contact
VssConnect support
contact@vssconnect.com
Q: Why is the item field blank for some of the records in my project history?
A: This is due to a bug in some versions of the Source COM API. Install Visual Source Safe 2005 on the VssConnect server machine to fix this problem.
Q: Does VssConnect work with Visual SourceSafe 2005?
A: Yes, in fact Visual SourceSafe 2005 is the preferred version of SourceSafe to use with VssConnect.
Q: What is the advantage of installing Visual SourceSafe 2005 on the VssConnect server machine?
A: When Visual SourceSafe 2005 is installed on the VssConnect server machine, the following features are enabled...
- Checkouts made using VssConnect appear to
be checked out to the correct local folder and machine when viewed with the
Visual SourceSafe UI.
- Check out comments are supported.
- User impersonation is supported. This allows
the VssConnect service to run under an account with limited permissions since
SourceSafe access is carried out using the connected user's identity.
- Pinned file support is improved.
Q: Does VssConnect work with Visual Studio 2005?
A: Yes, VssConnect does work with Visual Studio 2005.
Q: Do SourceSafe add-ins work with VssConnect
A: Although this has not be tested, add-ins do seem to work in VssConnect. Just remember that the add-in must be loaded into the
VssConnect server, not the VssConnect client i.e. the add-in must be installed and registered on the VssConnect server machine.
Q: Does VssConnect support shadow folders.
A: Yes, shadow folders should be updated when using VssConnect. If they are not, then check the VssConnect service account or VssConnect user permissions to make sure that the shadow folders are accessible.
Q: When I try to select Source Safe as the current source control provider, it
seems to be selected for a couple of seconds and it then switches back to
VssConnect.
A. There appears to be a bug in the source control provider switching logic
that results in this problem. Error checking has been added to the latest
release that should prevent this problem occurring again however, the registry
needs to be modified in order to fix the problem if it is already happening on
your machine. The steps are as follows.
Delete the registry value '_SCCServerPath' from the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe'
Make sure the registry value 'SCCServerPath' in the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe'
contains the location of the Visual Source Safe DLL, SSSCC.DLL. By default the
path to this file is 'C:\Program Files\Microsoft Visual Studio\Common\VSS\win32\SSSCC.DLL'
Once this has been done VssConnect should show that the current source control
provider is Source Safe and you should now be able to switch between providers
without a problem.
Q: Sometimes the VssConnect server stops accepting client connections and I have
to re-start the server. Is there anything I can do to prevent this from
happening?
A: This issue may be caused by the following Source Safe issue. Try updating Visual SourceSafe on the VssConnect server machine. If you
are using Visual SourceSafe 6.0, make sure you have 6.0d build 31222. This
version is only available by installing
Visual Studio 6, SP6 on the VssConnect server machine.
Alternatively, install Visual SourceSafe 2005 on
the VssConnect Server machine.
Q: I cannot login to VssConnect, it is telling me that the username/password is
not valid.
A: Make sure that the user you are trying to login as has a valid OS account on the
VssConnect server machine.
Q: Why do I get the error 'Access to file \\servername\sharename\data\a\aaaaaa denied' when I get a file history?
A: Try updating Visual SourceSafe on the VssConnect server machine. If you
are using Visual SourceSafe 6.0, make sure you have 6.0d build 31222. This
version is only available by installing
Visual Studio 6, SP6 on the VssConnect server machine.
Alternatively, install Visual SourceSafe 2005 on
the VssConnect Server machine.
Q: Why doesn't VssConnect register itself as a separate source control
provider.
A: When Visual Studio source control integration is enabled, VssConnect registers
itself as 'Microsoft Visual Source Safe' and not as a separate source control
provider. This is done because of the way Visual Studio handles source control
integration. This is best explained with an example. Let's say we are local to
the Source Safe database and we are working on a Visual Studio project using
Visual Source Safe as the source control provider. Visual Studio records the
name of the provider in the workspace file. Then we want to work on the project
using VssConnect as the source control provider. If VssConnect registers itself
as 'VssConnect' in the registry, Visual Studio will see the change in source
control providers and request that the workspace be checked out so that it may
record the change of provider name. Again, when we are back at our local site,
Visual Studio will want to check the workspace out again to change the source
control provider name. This behavior is undesirable to say the least and the
only way to remedy this is to pretend to be 'Visual Source Safe'. If you think
about it, it actually makes sense because the source control provider is still
Source Safe even when VssConnect is being used. VssConnect is just a proxy for
Visual Source Safe.
Q: When I run the VssConnect client I get the message 'Failed to connect! : The
type initializer for "System.Net.Dns" threw an exception.'
This is caused by a documented bug in the .NET framework. See the following Microsoft KB article.
Q: Why do the comments in the project history seem to be duplicated?
A: This appears to be a SourceSafe COM bug. Installing Visual SourceSafe 2005 on the VssConnect server machine rectifies this issue.
Q: Undo check out options do not seem to have an affect in VS.NET 2002.
This is due to a bug in VS.NET 2002. The issue is resolved in VS.NET 2003.
Q: I get the error 'The type initializer for 'NZlib.Compression.6441f0116640a15f' threw an exception' when using VssConnect with Visual Studio 2005, what can I do?
This error can occur when using VssConnect 1.4. Upgrade to VssConnect 1.6.
|
