Search found 3585 matches

by jclausius
Tue Jun 09, 2020 3:39 pm
Forum: Support (Vault)
Topic: vault.exe: GETTIME
Replies: 13
Views: 9440

Re: vault.exe: GETTIME

Yes.
Thomas Linder Puls wrote:
Tue Jun 09, 2020 9:00 am
If I understand this correct, then the GETTIME I have wished corresponds to a GET with an -ENDDATE option.
You're welcome. Thank you for being patient and using work-arounds until we implemented it.
If that is the case then thank you :-).
by jclausius
Tue Jun 09, 2020 7:22 am
Forum: Support (Vault)
Topic: vault.exe: GETTIME
Replies: 13
Views: 9440

Re: vault.exe: GETTIME

The new options for -BEGINDATE and -ENDDATE will be seen Vault 10.1, tentatively scheduled to be released this week.
Thomas Linder Puls wrote:
Tue Aug 28, 2018 5:27 am
vault.exe have comments GET, GETLABEL, GETVERSION.

We could very much use a GETTIME that will get files corresponding to a certain time stamp.
by jclausius
Tue Jun 09, 2020 7:21 am
Forum: Support (Vault)
Topic: Visual Studio 2019 Vault Pending Changes not displaying properly
Replies: 6
Views: 4997

Re: Visual Studio 2019 Vault Pending Changes not displaying properly

Having to turn off "Optimize Rendering for screens with different pixel densities" will be resolved in Vault 10.1, tentatively scheduled to be released this week.
by jclausius
Tue Jun 09, 2020 7:20 am
Forum: Support (Vault)
Topic: VS 2019 Pending Changes Window Hangs, Indefinitely
Replies: 7
Views: 6802

Re: VS 2019 Pending Changes Window Hangs, Indefinitely

Having to turn off "Optimize Rendering for screens with different pixel densities" will be resolved in Vault 10.1, tentatively scheduled to be released this week.
by jclausius
Tue Jun 09, 2020 7:17 am
Forum: Support (Vault Professional)
Topic: VS2019 Vault Pro extension
Replies: 23
Views: 16391

Re: VS2019 Vault Pro extension

Having to turn off "Optimize Rendering for screens with different pixel densities" will be resolved in Vault 10.1, tentatively scheduled to be released this week.
by jclausius
Fri May 29, 2020 2:25 pm
Forum: Support (Vault)
Topic: Auto Search change from v6 to v10
Replies: 10
Views: 6201

Re: Auto Search change from v6 to v10

Just to provide you with a bit more background info. The Repository Search was implemented in Vault 9 ( Dec 2015 ). As mentioned, on large, large repository trees, users would leave on the search feature quite often, and had performance problems when clicking around the repository (changing folders ...
by jclausius
Fri May 29, 2020 8:28 am
Forum: Support (Vault)
Topic: Auto Search change from v6 to v10
Replies: 10
Views: 6201

Re: Auto Search change from v6 to v10

No problem. We definitely welcome valid feedback. The first post just mentions to launch a search when clicking a repository folder. In order to make sure I have all the details, could you please elaborate on what extra functionality and the problems are solved by the “auto search on folder selectio...
by jclausius
Tue May 26, 2020 10:42 am
Forum: Support (Vault)
Topic: Auto Search change from v6 to v10
Replies: 10
Views: 6201

Re: Auto Search change from v6 to v10

In addition to the perf hit when changing folder to folder, the change was also necessitated to remove instabilities constantly producing incorrect results or causing other reported bugs and problems in the GUI client as users quickly changed from folder to folder. Stability/correctness of the resul...
by jclausius
Tue Apr 14, 2020 7:49 am
Forum: Support (Vault)
Topic: Error migrating VS2015 to VS2019
Replies: 1
Views: 1540

Re: Error migrating VS2015 to VS2019

Starting with Visual Studio 2017, Microsoft changed the architecture for pulgins within Visual Studio. These changes were implemented starting with Vault 10.0. This is called the Vault Standard/Professional Visual Studio Extension. To install within Visual Studio, you now have to use the Extensions ...
by jclausius
Tue Apr 07, 2020 9:57 am
Forum: Knowledge Base (Vault)
Topic: Vault Client performance issue on startup
Replies: 0
Views: 6646

Vault Client performance issue on startup

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...
by jclausius
Tue Apr 07, 2020 9:52 am
Forum: Knowledge Base (Vault Professional)
Topic: Vault Client performance issue on startup
Replies: 0
Views: 4975

Vault Client performance issue on startup

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...
by jclausius
Fri Apr 03, 2020 1:33 pm
Forum: Support (Vault)
Topic: vault.exe: GETTIME
Replies: 13
Views: 9440

Re: vault.exe: GETTIME

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...
by jclausius
Thu Feb 20, 2020 8:18 am
Forum: Support (Vault Professional)
Topic: GUI Problem with HighDPI Resolution
Replies: 25
Views: 11753

Re: GUI Problem with HighDPI Resolution

@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.
by jclausius
Mon Feb 10, 2020 1:25 pm
Forum: Support (Vault Professional)
Topic: GUI Problem with HighDPI Resolution
Replies: 25
Views: 11753

Re: GUI Problem with HighDPI Resolution

Can you see if build 10.0.3.31070 fares any better?
by jclausius
Mon Feb 10, 2020 1:16 pm
Forum: Support (Vault Professional)
Topic: The Check In/Commit transaction failed
Replies: 1
Views: 3813

Re: The Check In/Commit transaction failed

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 ...