Update on Team Explorer in Visual Studio 2017

Last month, we shipped Visual Studio 2017 RTM and since then we’ve had many reports on Team Explorer issues.  In a nutshell, the quality of Team Explorer in Visual Studio 2017 RTM isn’t up to our usual standards. Most of the bugs stem from 2 sets of changes: a major refactor of the authentication library and moving the Git experience from Libgit2 to Git for Windows. Those changes enabled us to add new features, as well as other Git features we haven’t released yet, but the changes weren’t high quality. We’re working to ship fixes as fast as possible.

Going forward, we’re making several changes in how we work so this doesn’t happen again.

  1. Expand our test matrix to cover more use cases with a specific focus on different network configurations
  2. Engage the community earlier on design changes and make sure those make it into early preview builds
  3. Deliver major architectural changes into preview builds earlier

Please keep sending your feedback using the Developer Community site. That’s the best way for us to track and fix issues.

Upcoming fixes

We’re making the following fixes to Visual Studio Team Explorer, as well as Team Services, between now and Visual Studio 2017 Update 3. Most of the issues will be fixed by Update 2, but some will wait until Update 3.

Fixed in Visual Studio 2017 Update 1

Fixed in Visual Studio 2017 Update 2 (current preview).  You can find out how to participate in previews in this blog post.

Fixed in Visual Studio 2017 Update 2 (next preview). You can find out how to participate in previews in this blog post.

To be fixed in Visual Studio 2017 Update 3

To be fixed on Visual Studio Team Service (we found a service side fix)

6