SourceGear Support

Thanks, I didn't know that needed to be called since all other operations were using the correct repository and Client.ActiveRepositoryID was the correct value, but after calling SetActiveRepositoryID() with the same value it worked.

I'm trying to use Client.GetRepositoryAt(txid) to get the way the repository looked at a certain version but it isn't working for my repository. I created a new repository and moved some folders around to get 5 versions and it seemed to work fine for it: var rep = ServerOperations.client.ClientInsta...

I don't actually need to find the file. I know its there at Version 1 because the history told me. I just need to be able to construct a VaultClientFile object for this version of the file . Then I would expect it to be able to return me the actual file from the Server. Its highly unlikely the file...

I'm writing tests as I learn to use vault and to understand exactly what the api calls do and I can't get this one to work reliably. Here I create two folders which puts them into a Pending Change Set in the client: ServerOperations.ProcessCommandCreateFolder("$/VaultWrapper.Tests"); Serve...

jclausius wrote: Check the VaultLib.VaultHistoryType members or use VaultHistoryType.GetHistoryTypeName(int) to convert the history types to their English strings.

EXACTLY what I was looking for (except it doesn't have type 230 which I'll ignore, using Vault 6.1), thanks!

Thanks for the quick response. That's the method I'm using, I just don't know what the values mean in the HistItemType field in the results. I think I know what those ones above mean, but I also see there are some history items with HistItemType values of 40, 120, 130, 150, 160, 180, 190, 220 and 23...

Are the possible values for HistItemType in VaultHistoryItem (and other fields) found by calling ServerOperations.ProcessCommandHistoryEx() listed anywhere? I'm trying to use this list but I'm not sure what the values are supposed to mean. HistItemType 10 = Add Child (MiscInfo1 has name of child, Na...

I know this is old but I thought I would add my 2 cents in case anyone else came across this. You could get the version of the parent folder using GetOperations.ProcessCommandGetVersion() I think. I use GetOperations.ProcessCommandGetVersionToLocationOutsideWorkingFolder() personally and it works ex...