SourceGear Support

Did your version of VS2003 ever work with Vault? I ask because some versions of VS don't support source control integration. The easiest way to turn this on is to go to the Vault GUI client, Tools->Options->Make Vault your default SCC provider, and toggle it. If it is already on, then turn it off, e...

Vault should be able to handle files of any kind or size - they are all the same to the backend server.

And Vault does support showing differences for text files, but not for files that are treated as binary, like image files or Word documents.

If you invoke history, the History Query Filter/Sort dialog is initially displayed (unless it has been turned off, in which case, go to Tools->Options->Command Dialogs to turn it back on). In that dialog, there are two radio buttons corresponding to viewing history by item or version. You will want ...

The short answer is: this is expected after a deletion of the cache. The long answer: When the cache is deleted, the baseline file gets deleted as well. The baseline file is the last version of the file retrieved to the client before it is edited. When the baseline is deleted, Vault has no way to de...

Add the attached .so file to the location where the other sgdm .so files are, and after restarting the tool, it should be available.

My only suggestion would be that if you want to work on both a trunk and a branch on the same machine, it would be convenient for you to use different working folders for them, so you don't have to switch them around, and you could also work on both at the same time. It may be that it isn't merging ...

If by Vault ID you mean the user name, then yes, if one process sets the working folder and another sets it again, the last one to set the working folder will be the way it stays. However, if you doing a full get to a new folder everytime, you probably don't want to use a working folder Get, but a G...

Does your Vault GUI client work properly on the same machine? One thing you could try is to turn on Vault client logging. See the knowledge base for how to set that up. You should be able to create a [yourapp].exe.config file that generates a log, and it might have better info about what is happening.

Another way to handle this would be set the option to not automatically commit operations, then delete the files one at a time, which will put them in your pending change set instead of immediately committing each one. Once you have deleted all the files, commit them from the pending change set, and...

This is just a guess, but follow the steps in this KB article and see whether that helps at all:

http://support.sourcegear.com/viewtopic.php?t=231

This is unlikely to be a Vault-specific issue, but there might be an interaction between VS and source control plugins that reveal a bug somewhere. In any case, the way to test this would be to turn on Vault IDE logging, and check whether any API calls are made to Vault as a result of pressing F7. S...

You can only put files under source control that exist within the project root, and references don't actually exist in the project source unless you copy them there. One workaround would be to copy the dll to a location within the project and explicitly add the dll file to project. VS will then reco...

Can you describe the exact problem you are having, and the steps to reproduce it?

Is the problem that the dll is not being included when adding the project to source control?

Are the files that are reported as checked out by VS read-write on disk? VS sometimes interprets a file that is read-write as checked out, even though it really isn't.

Yes, this is how it was designed - to ignore white space for file diffs, but not necessarily for folders diffs. I'll add this as a feature request (to add another option to ignore white space for folder diff). In the meantime, you can specify another diff tool in Tools->Options that supports the fea...