SourceGear Support

The bug's in line 481 of PluginServiceTemplate.asmx.cs - change it to:- ServerOperations.client.LoginOptions.URL = "http://" + hostname + "/VaultService"; ... and then the sample template's installation/registration process works. I put a value of $ in pathToWatch - is this ok? O...

Thanks Jeff. Btw, should we use the 64 bit or 32 bit version of SQL Server, or doesn't it make a difference to Vault?

We've found the solution - by default IIS wasn't configured to enable ASP.NET. The process for turning it on is documented here: http://support.microsoft.com/kb/315122

Jeremy, quick questions - what do you enter in the "path to watch" field? What is it used for? Edit: In the UpdateRepositoryInformation step, I enter the name of the repository & have taken various guesses at pathToWatch, but whatever I do, hitting invoke produces the following error:-...

Something else I'd like to suggest, fwiw. If I bring up a file's history I can't see the ID of the changeset for each revision number. It would be great if the changeset # was listed beside each file revision, perhaps with a context-menu action that allowed me to access the changeset's details and e...

Perhaps another thing you could consider. Let's say I've merged a branch into the trunk. In the branch I made 10 changes to the file, but all I see in the trunk file's history is the line where I merged it. Sure, the branch's history is there in text form, but that's not nearly as useful. It would b...

Ok Linda, thanks.

We've looked at a lot of products, but hardly any have a feature like this - if you added it, it would be another compelling reason to choose Vault over your competitors.

As I mentioned in a previous post, we're looking to move away from our ancient version of PVCS to a something with much higher performance and more modern features ... hence we're currently evaluating Vault. Although PVCS is old, there's one aspect of it that we've grown very used to, and which few ...

We've reproduced the problems that were causing 404 errors after an upgrade. The web.config was not getting modified correctly. Vault 4.0.1 will fix this issue, and for now the only workaround is to uninstall 4.0 (choosing to keep the database) and then reinstall 4.0 (choosing to keep the database)...

I'm currently evaluating Vault for a company with about 30 developers, looking to replace PVCS. The company has its own in-house bug tracking application which is integrated with PVCS using server-side event triggers. As there's no downloadable "server API" for Vault I'm wondering if this ...