SourceGear Support

Tara,

While we are working on addressing the issue, you can successfully use Vault with VS 2022 (17.1.7 - released May 10, 2022 or earlier updates).

Thanks,

Tonya

Tara,

Thank you for the confirmation. There appears to be a problem with Vault in the VS 2022 17.2.x build. We are currently working on a resolution and I will let you know as soon as it is available.

Tonya

We'd also like to know the exact build that you have of Visual Studio 2022.

Thanks,

Tonya

Tara,

We believe that you may have a corrupt download of the Vault extension for VS 2022. Can you please try to start over with a brand new install? This would require you to download the Vault extension from our download page again. Please let me know the outcome.

Thanks,

Tonya

Hello again,

Thank you for the update and I'm glad to hear that you were able to figure out where the problem occurred.

Tonya

Hello again, So just to confirm, you can connect to your Vault Server using your Vault GUI Client and within Visual Studio 2010? The problem only resides in Visual Studio 2022? Did it ever work correctly? If so, the problem began immediately after you cleared your client-side cache file? Can you ple...

Hi Tara,

A couple of questions for you.

1) Where did you download the VS Vault extension from? Our download page on our website?

2) What happens when you try to connect using the Vault GUI Client? Any errors?

Thanks,

Tonya

Sorry to hear about your shadow folder issue. We recommend during an upgrade with Shadow Folders configured: 1) The .NET permissions change in some versions. In some cases, you may need to set permissions on your Shadow Folders to allow the VaultShadowFolderAppPool to have read/write access. 2) If y...

Hi Vij,

I have copied below a link that will assist you with reporting:

https://download.sourcegear.com/misc/va ... ports.html

There is an option to run security reports so hopefully this will provide you with the information you are looking for.

Thanks,

Tonya

Hello again,

Thank you for the update and glad to hear things seem to be working correctly for you.

Tonya

Hello, Thank you for the immense details! I've spoken with our dev team to see if they have any suggestions: 1) Exclude the files from being checked in using either the Vault Admin Tool or Visual Studio. 2) Move the files from your working directory. 3) Try adding the project from the Vault GUI firs...

Hello again,

It should be the default port. Like you said, typically port 389.

Tonya

Hi Jeff, Sorry about the confusion on my part. Vault uses the System.DirectoryServices.DirectoryEntry to connect to the AD Server with the default option of connecting with the "Security" parameter. According to the Microsoft documentation, "security" is: Requests secure authenti...

Hello,

All communication between the Vault client and server is done over HTTP and utilizing IIS Web Services. You can configure IIS for SSL support to keep your data secure.

Please let me know if you have any additional questions.

Thanks,

Tonya

No, the Vault Server Database requires a Microsoft SQL Server.

Thanks,

Tonya