SourceGear Support

The Vault command-line client can be run on Intel Macs with the help of Mono , a free, portable .NET runtime. Installing Mono Download and install Mono for Mac OS X Runtime from the Mono Downloads page. The .dmg image contains an installer package and an uninstall script. You will also need to creat...

When viewing a file or folder's properties, you can right-click on the "Name:" field (General tab) and copy the path from there. It's a few more clicks, but it's available now! :-) "Properties" is available from the File menu or context menu. Alt+Enter works too. Your suggestion ...

Hello, Andy. It would help us to know which versions of Vault and CruiseControl you are using. From your log, it looks like you're using Vault Professional, but is it 5.1.0 or 5.1.1? And is it CCNet 1.4 or 1.5? One thing I can recommend is that you look into CCNet's "Integration Queues" fe...

BTW: If you do go back to using the Fortress plugin, you'll need to change "vaultproplugin" back to "fortressplugin" in your ccnet.config. The Fortress plugin will connect to either a Fortress or a VaultPro server.

Oops. Even though we included a BATCH command in the vault command line, our brains immediately switched to MS-DOS mode. Unfortunately, the file that you pass with "vault BATCH filename" must consist of vault commands, and there is no provision for "comments," or ignored lines. T...

When you do this, does it seem to be as fast as it was in the older version?

Hello, Neal. Here's something you might try: Next time you check in (or out), click on the "List" tab in the dialog. This is essentially the same view as we had in the old version, and it is faster to load. Your choice will be remembered, and subsequent checkins will default to the List vi...

Sorry for the confusion. Yes, in upgrading the Vault Demo server to 5.0 we reconfigured how it handles demo logins (among other things), and it ended up with a new database. Thus, the repositories that were on the version 4 demo server (RepositoryA, RepositoryB, VaultA) disappeared with the old data...

A couple of comments: I don't think that would work for us, leaving the VSS server around isn't the desired result after moving to Vault. For Handoff, all you need is a copy of the VSS database. It can be a local copy on your Vault server with no outside access. If you currently use a server to prov...

In Vault 5.0 / Fortress 2.0 we introduced our new Handoff feature, which performs a fast import of the latest versions from a VSS database and offers on-demand access to earlier VSS versions. Handoff requires the 32-bit Vault/Fortress Server, with IIS running in 32-bit mode. After a standard install...