Set the build type to 'Release' (this is important!).Open the resulting libssh2.sln in the build directory

wherever you extracted the source to)Ĭmake -DCRYPTO_BACKEND=WinCNG -DBUILD_SHARED_LIBS=OFF -DBUILD_TESTING=OFF -DBUILD_EXAMPLES=OFF.

You can use older, but don't as you'll need to fix some build issues in VS2015.ĭo the following: cd (e.g.

libgit2 source (grab the source from VS 2015 as noted in BPas's link).

See the link in BPas' post for the basic stuff, e.g. Here's some basic instructions for Visual Studio Update 2 and Update 3. The GitHub extension is open source, so it's possible that it may be able to use a different connection mechanism and begin supporting SSH before the core Git support in Team Explorer.

However I cannot make any predictions as to when support might be available. Microsoft is going to begin including OpenSSH in Windows (and is a sponsor of that very fine project). That said, we are working on it, and making progress. This is regrettable, but there are a handful of reasons why this is not available yet: the short answer is that in our opinion, providing SSH poorly or insecurely is worse than not providing SSH at all, and we would like to be very confident that any SSH implementation we provide is of high-quality. This is true even with GitHub repositories using the GitHub plug-in (which - at present - uses the same connection mechanism for Git repositories as any other Git repository using Team Explorer.) Visual Studio 2015 (RTM) does not support SSH for Git remotes.

Git visual studio code ssh key setting