Craig E. Shea

@pmiossec Long file path support was added in .NET 4.6.2. However, it still requires a user to "opt-in" to long file path support on Windows itself through a setting in...

Actually, this is desirable behavior for me. I _want_ to clone the deleted branches in order to preserve as much history as possible. So, maybe we need an additional configuration...

@jhudsoncedaron There is a way to "manually" create the commits you need, but it's very time consuming. I don't have proper instructions to give because I did it very manually--afterwards,...

So, I was doing some research on this. It appears the v15 TFS Client libraries are still in pre-release. This would seem to me to imply that the v14 libraries...

**UPDATE**: I see an attempted registry access in the error trace above, looking for `HKCU\Software\Microsoft\VisualStudio\14.0`, and as we all know, that's definitely a VS2015 related registry key. Hmm... I'll keep...

And I see that there was a stable release of the v15 Microsoft.TeamFoundationServer.* NuGet packages--so hopefully we should be able to make this work. 😄

@SheGe Yes, VS2017 no longer installs many registry keys at all! In this regard, VS2017 is vastly different from previous versions of Visual Studio. In fact, it's this change that's...

I'm very happy to report that I found what I was looking for. I thought `Microsoft.Visualstudio.Teamfoundation.TeamExplorer.Extensions` was a DLL, but it was a Visual Studio extension package ID. And once...

I believe that I have a working version of git-tfs against Visual Studio 2017. I successfully synchronized one of my branches between TFS, my local repo, and the centralized git...

@SoonDead, @SheGe Would either one of you be able to test out the PR #1056, especially for check-ins to TFS? I may not get to testing that for a day...