{"id":30865,"date":"2017-04-24T07:15:24","date_gmt":"2017-04-24T15:15:24","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/?p=30865"},"modified":"2019-02-14T15:51:52","modified_gmt":"2019-02-14T23:51:52","slug":"update-on-team-explorer-in-visual-studio-2017","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/update-on-team-explorer-in-visual-studio-2017\/","title":{"rendered":"Update on Team Explorer in Visual Studio 2017"},"content":{"rendered":"

Last month, we shipped Visual Studio 2017 RTM and since then we\u2019ve had many reports on Team Explorer issues.\u00a0 In a nutshell, the quality of Team Explorer in Visual Studio 2017 RTM isn\u2019t up to our usual standards.\u00a0Most of the bugs stem\u00a0from 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\u00a0new features<\/a>, as well as other Git features we haven’t released yet, but the changes weren’t high quality.\u00a0We\u2019re working to ship fixes as fast as possible.<\/p>\n

Going forward, we\u2019re making several changes in how we work so this doesn\u2019t happen again.<\/p>\n

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

    Please keep sending your feedback using the\u00a0Developer Community<\/a> site. That\u2019s the best way for us to track and fix issues.<\/p>\n

    Upcoming fixes<\/strong><\/h5>\n

    We’re making the following\u00a0fixes 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.<\/p>\n

    Fixed in Visual Studio 2017 Update 1<\/strong><\/p>\n