SourceGear Support

A performance issue has been discovered for Vault Clients up to 10.0.x in which the entries of a client side cache file (CacheMember_PendingServerNamespaceChanges) hinders performance of the client upon startup. Vault 10.1 will introduce code changes to help mitigate the problem of the extraneous en...

A performance issue has been discovered for Vault Clients up to 10.0.x in which the entries of a client side cache file (CacheMember_PendingServerNamespaceChanges) hinders performance of the client upon startup. Vault 10.1 will introduce code changes to help mitigate the problem of the extraneous en...

We've implemented some new options ( -BEGINDATE and -ENDDATE ) in GET and GETWILDCARD to provide this functionality. It works by taking 3 different combinations: -BEGINDATE (only) : Get all files where the file's TxDate is greater than or equal to the timestamp argument - ENDDATE (only) : Get all fi...

@BigBrett, did you get a chance to try build 31072 yet?

BigBrett wrote: ↑

Tue Feb 11, 2020 10:18 pm

My bad - I do have 31070 that replaced 30936.

Can you see if build 10.0.3.31070 fares any better?

It could be the client side cache has some invalid data. My first recommendation would be to : - Shut down the Vault Client - Clear the client side cache for the repository only ( See https://support.sourcegear.com/viewtopic.php?t=11513 ) - Restart the client to get a refresh of the repository from ...

We noticed that Microsoft turned it back on in an update, and are currently working on a fix. If anyone on Vault 10 is interested in a private build that may address this issue, please email 'support AT sourcegear DOT com' with a link to this forum posting.

You're welcome. I'll update the post once there is more info.

You're welcome.

JetBrains got back to me with a status update: Since TeamCity 2019.2 we no longer bundle Vault plugin with TeamCity distributive. In the latest versions we've been unbundling some plugins aiming to reduce the size of TeamCity distribution and lists of supported runners, tools and version controls on...

Thank you.

FWIW, I reached out to a couple of contacts I had as well. I have no idea if they're still with JetBrains, so who knows if I'll hear back. Between the two of us, perhaps we can get some kind of status update.

We haven't heard from JetBrains folks for a bit of time, and they'd be able to better answer questions about decisions made on TeamCity. Have you posted anything on their forums regarding any kind of change?

This is the first request we've had regarding a 64-bit implementation of the Vault Classic Client. I've recorded the information you've posted here to investigate. At this time, it probably won't get answered until after the new year. I wish it was simple as a recompilation, and off it goes. Since t...

If only .NET 4.0 is installed, it could be you need to configure the Vault IDE plugin to use .NET 4.0 - since by default it will try to host a .NET 2.0 environment, and that isn't installed. Installing .NET 2.0 Framework would be the easiest thing to try, but that is sometimes not practical. For tho...

Is the process loading the VaultIDE.dll a .NET Framework based process? One of the requirements of VaultIDE.dll is that the calling process *must* be a .NET Framework based application OR a compiled (using something like a C-runtime) application, but the .NET Framework installed (as the Vault IDE.dl...