SourceGear Support

In Vault, I look at the differences between the baseline version and working version of a file in Visual Studio project. This opens DiffMerge 8.0.1, baseline version on the left, working version on the right. The are some differences. I press toolbar button "Jump to the next change", and t...

Didn't help. Let's try other things!

I have an application (Wise Installer Editor) that is source-control-capable; but when I'm trying to configure it, it says: "To use the source control features, you must have a source code control system (such as Microsoft Visual SourceSafe) installed on your computer. No source code control sy...

Just as a friendly suggestion: I think, the most solid solution would be if the client figured out from the server that the file is read-only already at the opening, and set the mode appropriately. A real file also can be read-only, so this would be useful there as well - it's like MS Word works whe...

btw, regarding the version, here's kinda bug report, a cosmetic issue. Even though DiffMerge in Vault says it's 4.1.4, it's Help says it's 3.2. Those rare individuals who know how to press F1 may be confused

Thanks for the clarification.

> but in the case of diffing 2 historical versions, it is the right thing to do.

I'd think, it should be Vault that should make impossible editing of the historical versions by any client, rather than relying on the client not to do it.

I'm using DiffMerge from within Vault. Here lies confusion #1: according to Help/About in DiffMerge, it is version 4.1.4 ; but here on the website I see "DiffMerge 3.3 is now available". So, what do I have? The main problem however is this. I see that I can edit the right panel or apply de...

so what I'm saying is, if building the file takes so much time (as I understand, depending on the number of incremental versions since), it would make sense to somehow let the user know that this is normal. I killed the process several times before I realized what's going on, because that's what you...

emailed log file. According to the word "delta" in the log messages, it does look like by design, i.e. I think it had to retrieve some chain of versions to get to the right one.

I'm trying to get a file from history results. I select the version about 10 versions ago, and Get it. The progress bar relatively quickly reaches 100%, after which there's no further progress for couple of minutes. Looking in %temp%, I see how vaultclient is writing .tmp file, the size is growing t...

> It wasn't clear from your post whether or not the problem has been resolved

yes, once I moved the file to the right place, everything worked.

I had the same issue again; this time, I already opened not the group but regular VB6 project; one of the files in the project was new, recently created; I tried to add it to Vault, and it did not work. The log file is attached. By the way, producing the log file was problematic as well. When vb6.ex...

1. Unknown means "present but Vault can't tell what it is". Perhaps a different status here would eliminate the confusion, such as "Not Set" or "No Working Folder" It seems to me, "Unknown" means "can be any", including "absent". It does n...

Thanks for the reply Linda; couple of cosmetic suggestions... 1. if there's no working folder, the status should be "unknown" rather than "missing". "Missing" is plain misleading and somewhat scary for the user. 2. maybe it would be even more clear if when the status is...

Hello, 1. In Vault Client 4.0.4, I create new folder $/MyFolder; then I right-click on it, select "add files/folders", and add c:\autoexec.bat. Autoexec.bat appears in the Contents pane, however, status = "Missing". Why "Missing"? If this is because I did not set workin...