SourceGear Support

While on the topic, if I upgrade our license to 4.0 is there anything preventing us from continuing to use 3.5?

I've been in the process of transferring our VSS databases over into Vault. What baffles me is that sometimes the process proceeds rather quickly, but other times it's painfully slow. I transferred over a 9 GB VSS database in just over 10 hours, but now I've had a 2 GB database running for three day...

Actually, I got it working using Connection.ListUsers. The Connection.GetUserList is what I was using before, and that returned a list, but the isActive was always false and the Status was always 0. The one thing I noticed about the Connection.ListUsers is that it only works if you're logged in as a...

That's good to know, but the trouble is that I get a status of 0 for every user, regardless of their actual status.

I'm retrieving a list of users with the GetUserList function, but every user in the list is shown as having an isActive value of false and a Status of 0. Is there a reason for this? I want to see if the users are currently Active or Inactive, but this doesn't seem to be working for me.

Ok. The Vault path I was working with was "$/Systems/HHMI288/ActiveLink/NAV to AS/Department". In my code building application, I ran the TreeCache.SetWorkingFolder passing in a Vault path of: "$/Systems/HHMI288/ActiveLink/NAV To AS/Department". The only difference being the &quo...

Eureka! I figured out my problem. There's apparently some case-sensitivity involved in the SetWorkingFolder. The folder name in question is "NAV to AS". The path I was passing into SetWorkingFolder had "NAV To AS". Apparently that really hoses things up.

Ok, this just keeps getting stranger. We've got an application to build code using the Vault API, and when it runs the SetWorkingFolder function, it brings about the situation I've described. When I set the working folder through the Vault client, it works just fine. So as a test, I threw together a...

Explicitly set.

I've seen a strange problem today. I've got a repository folder which shows in the Vault client as having no working folder. I try setting the working folder to the desired local folder and it gives me a message saying that the local folder is already a working folder. Which I've seen before. What's...

Yep, that did the trick. Thanks!

How do I tell if a VaultDeletedObject is a file or a folder? I believe it has something to do with the Properties value of the VaultDeletedObject, but I'm not sure what the deal is with that. Most objects seem to have a Properties value of 1 or 2, which seems to correspond pretty well to folder and ...

What I think would be the ideal situation would be to offer the user the following choices when they try to get latest to a Vault folder that has a different working folder already assigned: 1) Allow the user to cancel the operation, which is the only option avaliable now. 2) Allow the user to ignor...

That works great! You have my thanks.

I'll log a feature request for this. Seems like a reasonable enhancement. Thanks. It's not a deal-breaker for us, since we can just remove the working folder assignment from the repository folder before getting files from the next repository folder. It's just that it's a bit of a hassle to have to ...