SourceGear Support

If you want to configure this, the best option is to configure things manually for the "IIS AppPool\*" related to Vault Server application pools.

The Vault server will need read/write access to %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys to initially create the "edb3 ...

Status Update:

We have identified a problem with Work Item Tracking in the Visual Studio Extensions. At this point in time, please contact SourceGear Vault Technical Support on providing a solution to the problem.

Thank you for your understanding.

Thank you for the report.

Thank you for your patience while we dig into the differences in how VS 2019 handles the Vault work items vs. VS 2022.

HI there,

The encryption between Vault client/server depends on an RSA key generated on the Vault Server. This file will have either "edb3..." in either the first or second portion of the file name (separated by an underscore).

The Vault Server security context of the Vault Server process will ...

Note, starting with VaultCPC Standard 11, setting the extended attribute using xattr should no longer be required. At least with this current implementation of Gatekeeper within MacOS.

Note, starting with VaultCPC Professional 11, setting the extended attribute using xattr should no longer be required. At least with this current implementation of Gatekeeper within MacOS.

In regards to history, there are two types of comments:

A transaction comment
A transaction Item comment


When you look at version history, it will display the Transaction comment only. Then when you view the details, it will show the transaction comment above and any transaction item comments ...

ProcessCommandVersionHistory() will list the transactions that have been applied to a given Folder.

With that said, any time an object in the repository is changed, the parent folder and all of the ancestor folders up to and including $/ are also bumped by a version. So, it isn't just changes, but ...

Yeah... the _sgbak is a folder full of files that are saved in the case of something catastrophic and you didn't really mean to undo a check out or overwrite a file on a GET. If you do NOT need the files, you can safely delete them. There are client side options for the backup directory as well ...

Due to state information of a repository possibly changing between versions the Vault client was written in such a way that only one version can work at a time. Each version of the Vault client stores some of the more system wide settings in HKLM in your registry and unfortunately are not versioned ...

I've logged a bug report for the trimming issue for unknown files to investigate a fix for the problem. I'll report back on that once I know more.

In the meantime, hopefully some of the work-arounds I've provided will allow you to avoid unknown file resolution altogether.

Note, when I say the Vault component sees files that it thinks it did not get, the Vault client has a client side cache for files it has retrieved and their state (checked out status list, time stamp, size, etc.). If you're running a builder where those pieces of the file cache file are not ...

Just to verify, you are using a GETLABEL command from the command line, and by using the -LABELFOLDER option you have configured the command line client with a working folder of "C:\JK\workspace\B@4\Repository\Trunk" and the working folder is either empty or you have populated it with a previous GET ...

Hi Thomas,

Could you please elaborate more on what you mean by recognize changes in .razor files?

For example, if I have a project bound, and edit the .razor file, the file shows in my pending changes pane upon editing the file. See attached
.

Here's a quick screen shot of the roles selected running Vault Server 10.2 on Windows Server 2022.