SourceGear Support

By default, the diff tool is configured to be read-only. You can change this in Tools->Options->Diff/Merge->Diff Arguments by removing the /ro1 or /ro2 arguments.

Good point Greg. Perry, how many files are in the folder that you are experiencing problems with? If you temorarily turn on the option to require checkouts, does it make the sluggishness go away? Or, is there a message saying "Looking for changes in working folders..." above and to the rig...

selfgov2000 wrote: On the status update, I believe I had first done a get latest to the folder, then set the working folder, and had to do a show diff in each folder for the gui to figure out the status.

Ah, I see. A Get Latest should resolve the files it can without having to diff each folder separately.

By Vault IDE client, do you mean the standalone GUI client, or the Visual Studio IDE with a Vault project loaded? If this is the standalone GUI client, again, is the status search pane in the foreground when you do this? There is a bug in the status search pane that it automatically starts searching...

Are the new folder requests going into your pending change set rather than immediately going to the server? Check the pending change set and also Tools->Options->Check In->Auto commit after each operation. If that is unchecked, operations such as Create Folder get put in the pending change set until...

Is it possible to label all files on or before a specific date in a branch without doing it to each file individually? You can do this from the history dialog. Do a history by version (which is a radio button in the history query/filter main tab), and then you can label a folder at a specific versi...

What error are you getting, and what rights do you currently have at the parent folder where you are trying to create a new folder? (Go to the Folder Security tab of the Admin Tool, and select the repository and parent folder and then find your name on the right list box of users).

Yes, destpath is exactly what you want, since you don't need the state of the files for later. It should run a little faster than a working folder get as well.

Vista isn't supported yet by Vault, and I don't believe anyone here has tried installing it yet.

Maybe someone else out there can chime in?

destpath is used to put files into a non working folder, meaning the state of the files will be unknown after the Get, because state is only determined when using a working folder. Using destpath to go to a working folder won't produce the results that you probably want, since it won't update the st...

I'm not the Nant expert, but take a look at the answer to this post http://support.sourcegear.com/viewtopic.php?p=25172#25172 Nant Vault tasks don't overwrite modified files as far as I know (unless your Get Latest option is set to overwrite). They do overwrite files that are old but checked out. Le...

Vault only overwrites changed files if you tell it to, and even then, it makes a backup in an _sgbak folder by default, just in case. The issue here isn't modified files, because on a Get Latest, you have the choice of overwriting them, not overwriting them, or merging the repository's latest change...

Maybe other folks out there have ideas or suggestions for how to deal with this, or perhaps asking the question in a Microsoft Visual Studio forum would yield some good answers. I'm pretty sure Vault doesn't really come into play in this scenario. It has the ability to store DLLs if you choose to go...

FYI, this bug has been addressed in Vault 3.1.9

We released another Vault dot release (3.1.9) today that includes a fix for the original issue in this thread (deleting a folder and adding another one of the same name causes files to be deleted on a Get Latest).

We still don't have a ship date for 3.5, but it should be this month or next.