Vault Extension for Visual Studio 2022

[jclausius]

This post is to inform everyone that we've uncovered a bug in Microsoft Visual Studio Update 17.2.x that prevents the SourceGear Vault Extension from working properly in that update.

Until Microsoft addresses the issue or we've been able to find and code a work-around to the problem, Customers wishing to keep using Vault integration within Visual Studio 2022 are encouraged to stay on Visual Studio 2022 Update 17.1.7 or lower. Note, Update 17.1.7 was released May 10, 2022.

Stay tuned to this thread for further announcements.

[jclausius]

We've isolated the problem in Visual Studio 17.2.0 and 17.2.1. The Vault Extension has a sub-extension that handles the authentication portion of the Vault client. When the Vault Extension is loaded, it registers this type with the object to use if another Vault service requests its usage.

In Visual Studio 17.0 through Visual Studio 17.1.7, later on when the Vault Client requests this service to get an authentication token to send to the Vault Server from a Vault related operation, Visual Studio returns the Service object which handles this. Starting with Visual Studio 17.2.0, this same code now returns NULL. We're not sure why that is the case. A report has been filed with Microsoft regarding the problem.

Until Microsoft responds, as of this posting Visual Studio 2022 Updates 17.0 through 17.1.7 are the only Visual Studio updates which will work with the Vault Extension for Visual Studio 2022. See https://docs.microsoft.com/en-us/visual ... tstrappers for Visual Studio 2022 17.1 .x bootstrap installers - either the regular release build 17.1.32428.221 or the LTSC version build 17.0.32428.209.

[jclausius]

Latest update (June 8, 2022) - The Microsoft developer evaluating the issue seems to believe the problem is not in the Vault Extension itself, but rather a change made to the VSIX Installer and how it registers "Sub" Vault Extensions used / packaged within the Vault Extension. Again this works in the Visual Studio 17.1.x code base.

The developer has passed the issue to the team working on the VSIX Installer, and they are supposedly going to follow up with more questions.

[jclausius]

Latest update (June 29, 2022) - Microsoft has released a patch within Visual Studio 17.2.5 that registers the Vault components correctly. We thank Microsoft for the fix introduced in the 17.2.0 and 17.2.1 updates. Vault customers wishing to use Vault with bound solutions and projects should use Visual Studio 17.0.x through 17.1.x OR upgrade to Visual Studio 17.2.5 (or later).

Please note, while this change *does* correct behavior within Visual Studio that allows Vault to register, there is a different outstanding issue the Visual Studio team has NOT addressed. This problem manifests when trying to invoke "Open from Vault" from the Visual Studio menu in order to retrieve a new solution and or projects from a Vault Server.

A current work around exists by getting the files on disk (and setting a working folder) using the Vault client. Afterwards, go into Visual Studio for the newly retrieved solution/project(s) and choose File -> Vault Source Control -> Change Bindings and bind the local project to the Vault repository. Afterwards, you may commit the modified (Source Control Enabled) solution and project files back into the Vault Server.