Integration with Visual Studio 2017

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear


Posts: 8300
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
PostPosted: Tue Mar 14, 2017 4:03 pm
Starting with Visual Studio 2017 Microsoft made a change that affects how third party Source Code Control providers register their integration components. What this means for Vault users is that after installing the Vault client, a secondary component needs to be installed in order to use the Vault Visual Studio Enhanced Client with Visual Studio 2017. As of Vault 10, a Visual Studio 2017 client extension can be found on the Vault downloads page.

Download the client called Visual Studio 2017 Extensions.
VS 2017 Extension.JPG
VS 2017 Extension.JPG (58.13 KiB) Viewed 228 times


The downloaded file is called VaultPro_VisualStudioExtension. Double-click to install.
Note, if the *.vsix extension is not registered on your machine, you may have to install via command line. The VSIXInstaller.exe binary, usually found in %VS150COMNTOOLS%, is used for this purpose. You can run VSIXInstaller /? to see the arguments required to install the Vault extension.

VSIX install.JPG
VSIX install.JPG (34.41 KiB) Viewed 228 times


The installer will only install the Vault Enhanced Client, and you will see this under Tools - Options - Source Control - Plug-in Selection.
Tools Options Source Control Plugins.JPG
Tools Options Source Control Plugins.JPG (34.83 KiB) Viewed 228 times


Limitations
The features Show History and Show Differences cannot work with only the VSIX client installed. For those features, the Vault Windows GUI client needs to be installed.
Beth Kieler
SourceGear Technical Support

Return to Knowledge Base (Vault)

Who is online

Users browsing this forum: Google [Bot] and 2 guests

cron