Error migrating VS2015 to VS2019

[andreypir]

I cannot find a way to migrate my VS2015 projects into VS2019. Steps to reproduce:
1. Use VS2015 to create a sample project, such as Windows Forms Application.
2. Use VS2015 to put the sample project to Vault.
3. Open the project with VS2019.
4. Error message is shown: "The project '...' is under source control. An error occurred registering this project with source control..." 2 times. It then shows error "One or more projects in the solution were not loaded correctly...". The project is unloaded, and it is not possible to load it - problem.

Windows 10 x64
Source Gear Vault Standard 10.0.2 (936)
VS2015 configured for "SourceGear Vault Standard Visual Studio Enhanced Client"
VS2019 configured for "SourceGear Vault Standard Classic Client"

[jclausius]

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 functionality within Visual Studio. The Extensions menu locations are different in VS2017 and VS2019, but if you can pull up the Visual Studio Extensions and search online for "Vault", you should be able download, shutdown Visual Studio and install the latest release of Vault Extension for Visual Studio.

If you cannot find it on the Visual Studio Extension marketplace, you can also download the VIsual Studio Extension from the Vault downloads page - http://www.sourcegear.com/vault/downloads.html, and install by either invoking 'Open' on the corresponding .vsix file or from the command line. Note, you'll need to find and use Visual Studio's VSIXInstaller.exe to install the Extension from a command line. ( Please post back if you need instructions for a command line installation. )

After the installation has completed, restart Visual Studio without opening any solution/project, go to Tools -> Options : Source Control, and change the Source Control plugin to the Vault Extension.

Please post back if that resolves the issue.

---

Note, when you configure Visual Studio with the Vault "Classic" client, that is an entirely different Vault plugin for Visual Studio. For that configuration to work, you would have to UNBIND everything within Visual Studio 2015, and re-bind using the Vault Classic client within Visual Studio 2015. Microsoft did NOT change the architecture for the "Classic" plugin platform. However, the solution / projects must all be bound to the Vault Classic client.