SourceGear Support

Neither worked.

Nope. Didn't work.

I'm not getting any events from that message. Here's my code: // ...snip... ServerOperations.GetInstance().UserMessage += GetMessageEventHandler; GetOperations.ProcessCommandGet(objectPaths.ToArray(), options); ServerOperations.GetInstance().UserMessage -= GetMessageEventHandler; // ..snip private v...

How do I get the list of files that were updated by GetOperations.ProcessCommandGet?

When I try and commit via the client API, I get an error: Type: System.Exception Commit failed at VaultClientIntegrationLib.ServerOperations.ProcessCommandCommit(ChangeSetItemColl csic, UnchangedHandler unchanged, Boolean keepCheckedOut, LocalCopyType localCopy, Boolean removeLocalCopy, Boolean reso...

I'm trying to create a revert command: I want to be able to undo all pending additions, deletions, and modifications at any point in my repository tree without affecting any changes outside that part of the tree. For example, if my tree looks like this: $ Current Production Database Web I would like...

If I update a file's timestamp, usually by modifying the file but not changing it, this is what happens: * When I choose "Commit selected operations..." in the GUI, the file is "un-checked-out" and the Version number of the file stays the same (it stays at 50). * When I run the C...

The file is Unchanged.txt. In my test, I read the contents of the file and then overwrite the file with those same contents, like this: var contents = File.ReadAllText(@"Unchanged.txt"); File.WriteAllText(@"Unchanged.txt", contents); And when I call var changes = ServerOperations...

How do I get the API to behave like the GUI with respect to unchanged files? In the GUI, if a file has been modified, but unchanged, it is updated so that it no longer shows as updated and a new version is not added to the file's history. When I commit via the API, an unchanged file gets checked-in ...

How do I attach to the UserMessage event. This: // ... snip ... ServerOperations.UserMessage += VaultMessagHandler // ... snip ... private void HandleUserMessage(object sender, string message) { // ... snip ... } gives me a compiler error: "Cannot access non-static event 'UserMessage' in static...

I've re-written my commit logic to commit a specific directory. But when I do that, my commit fails with a generic System.Exception: Commit failed message. Here are the two calls I'm making: ServerOperations.ProcessCommandAdd(@"C:\WorkingDirectory\", new string[] { @"C:\WorkingDirecto...

What about via the API? I don't see any flags on the ProcessCommandAdd that allows me to auto-commit. ServerOperations.ProcessCommandAdd(@"c:\WorkingFolder", new string[] { @"c:\WorkingFolder\d69e28dc-c58b-487c-a83c-e118f46ee2c4.txt" }) ServerOperations.ProcessCommandCheckIn(new ...

I'm now having a hard time committing add files, both via the command line and the API. These are my command line invocations: > vault.exe add -host vault -repository Repo c:\WorkingFolder c:\WorkingFolder\d69e28dc-c58b-487c-a83c-e118f46ee2c4.txt > vault.exe commit -host vault -repository Repo c:\Wo...

Here you go. File was too big, so I had to split it in half.

The ProcessCommandListChangeSet command now works much faster. I'm using it to see if an item has already been added, so I have to call ListChangeSet with the parent directory of the file being added. It also throws an exception when passed a file that doesn't exist in the repository whereas before ...