SourceGear Support

Not that Eric doesn't have enough to do, but having just read this thread for the 1st time, I'd like to push for Christian's suggestion of a best practices documentation along with a step by step how to implement them using Vault. It would definitely help as I see people asking these types of quest...

jwinn, I'm just posting to let you know that Dan is out of the office today and I think he's the only one here with enough history on this issue to provide clueful comments. He will return on Monday. In the meantime, I can confirm that in Vault 3.1.0, the IDE client never uses FileSystemWatcher. Sin...

I believe this is one of the bugs which was fixed in version 3.1.

Is storing binary files in Vault not recommended in general? We are thinking about storing versions of pruduct exes and redistritables in Vault. What are the catches of doing that? If the binaries are large, are they going to affect the performance of Vault in the long term? Vault handles binary fi...

Anybody here at SourceGear know if this problem was ever reproduced here?

Dragnet 1.0.4 is now available. For more info:

http://support.sourcegear.com/viewtopic.php?t=4298

Dragnet 1.0.4 is now available. For more info, see http://support.sourcegear.com/viewtopic.php?t=4298

The following features and changes have been included in the 1.0.4 release: Features: * Added a Resolver field so QA testers and others can track items assigned to them for verifying. * Open Items and My Open Items pages now list open items for assignees and completed items for Resolvers. * At-A-Gla...

Vault 3.1.0 is now available.

For additional details, see http://support.sourcegear.com/viewtopic.php?t=4294

Vault 3.1.0 is now available.

For additional details, see http://support.sourcegear.com/viewtopic.php?t=4294

Vault 3.1.0 is now available.

For additional details, see http://support.sourcegear.com/viewtopic.php?t=4294

Vault 3.1 is considered a major maintenance release for Vault 3.0. It is a free upgrade for all users of Vault 3.0. The changes and improvements in Vault 3.1 are too extensive to be consistent with a 3.0.x version number. A server upgrade from Vault versions prior to Vault 3.1 will require more upgr...

I never like to blame-shift away from a potential problem with our software, but this just smells like a problem with your machine. Can you rule that out somehow? Any errors in Event Viewer? Is your hard disk okay? Stuff like that. Another possible scenario is that Vault's client side cache files go...

Hydrogen wrote:Is the integration that difficult? This thread has been running for two years!

Difficulty is not the issue.

I don't have anything to announce yet, but I can say this: This feature is being taken seriously, and this thread is the primary reason why.

Suspecting that this might be a bug which we already fixed in Vault 3.1, I suggested John try the client from 3.1 beta 2. He reports that it worked with no problems.