SourceGear Support

The GUI client works fine, but the API does not. I copied the /vault folder over to another server and put it into /vaultservice and the API is connecting just fine there. The login() method of ServerOperations does this check, which forces "VaultService" onto the end. if (ServerOperations...

I may have found the problem. The ServerOperations class has a check for "VaultService" hard-coded in the login method and our installation is at https://myServerUrl/Vault I don't see a way to override this behavior in the API. I have the 5.1.1.19215 Standard version of the API files to ma...

I'm using Vault Standard 5.1.1.19215 with the matching API dlls and cannot connect to the server. If I use: ServerOperations.client.LoginOptions.URL = string.Format("https://{0}/VaultService", "myServerURL"); ServerOperations.client.LoginOptions.User = this.VaultUser; ServerOpera...

OK, thanks. I was just reading about Robocopy options and think I can also sync the timestamps between folders that way as well.

Yup, tried that many times. It doesn't actually do the get because the version numbers are the same.

I have a lot of local files that have their modified date out of sync with the repository, but their version number is the same. Is there a way for me to force a get all so that it replaces the local files with the correct timestamp? I'm using Vault 5.1.1 it seems that it only looks at the version n...

Yes, say I have the following structure: Project Alpha Repository Project Beta Repository Utility Project Repository I'd like to be able to have the Utility Project referenced in both Alpha and Beta solutions (and any others that will utilize the Utility Project) and not have to move to this structu...

I see some past posts about people wanting to share a common project across multiple repositories. It has been said that they could all be moved into one common repository, but it seems counter-intuitive to move multiple (or all) unrelated solutions into one repository just to be able to share a com...

I would like to see this as a feature, but it would probably require changing your installation procedure to not require SA access (a good thing in my mind regardless), and also would be best with a single database to save costs instead of two (sgmaster,sgvault)

Thanks, What I had to do was a bit more than that for my case. - I had the SQL Administrator do a backup of sgmaster and sgvault, then restored those into a local machine. - The existing web server could not connect to this database, so I installed Vault server onto the local machine and had it upda...

I realize it doesn't need to be the SA account - hence why I was referring to the role. Since this is an upgrade, and the database and account already exists that it's going to use, why not put an option in the installer to skip those commands and continue on? This would allow an account that is dbo...

Is there a way to perform an upgrade from Vault 5.01 to 5.03 without being sa or a member of the SQL sysadmin role? I have the sgvaultuser credentials that is dbowner, but the install script will not finish without being a sysadmin. I'm getting error -1280. Our IT policies will not allow for applica...

After using Fortress for some time, we're finding that we do not use the bug tracking capabilities much within the system. So rather than continuing to renew at the cost of Fortress, we'd like to migrate to Vault. Is that possible?

Thanks Linda,

I'm not sure how I'm seeing line history when I'm selecting Show History and not Line History from my code behind file, but I'll take a feature request to change this.

Using VS2008 and while in code view I right-click and choose Fortress->Show History, but it brings up the dialog to show the history for the .aspx file rather than the .vb file. Is there a way to get it to bring up the code file history without having to turn on Show All Files, then right-click on t...