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.
- Expand our test matrix to cover more use cases with a specific focus on different network configurations
- Engage the community earlier on design changes and make sure those make it into early preview builds
- 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.
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
- Solution appears to close immediately after opening(125 votes)
- VS 2017 Stops Responding / Freezes / Locks up(43 votes)
Fixed in Visual Studio 2017 Update 2 (current preview). You can find out how to participate in previews in this blog post.
- Bring back Showing Solutions File in Team Explorer Solutions Section(75 votes) / team explorer doesn’t show solutions inside git repository (10 votes)
- Git Commands don’t work when folder name has special characters(5 votes)
- Error when using Blame for Git repository “non-space character detected within the skipped tab prefix”(4 votes)
- Git history isn’t working(4 votes)
Fixed in Visual Studio 2017 Update 2 (next preview). You can find out how to participate in previews in this blog post.
- TFS folder download cause vs not responding(12 votes)
- Object reference not set to an instance of an object – Opening Team Foundation Server Project(11 votes)
- Git unable to start process (8 votes)
- Git: This conflict type is unsupported (7 votes)
- Git merge w/ commit UNchecked commits anyway(5 votes)
- I get ‘fatal: unable to access ‘\/.config/git/config’: Invalid argument’ when running VS 2017 as a user on a different domain from local windows user(5 votes)
- Downloading items from TFS2013 with Visual Studio 2017 (5 votes)
- Cannot connect to TFS 2017.1 when using different port and no virtual path from Visual Studio 2017 (5 votes) – this issue is really a grab bag of various issues; up to you whether you want to include it
To be fixed in Visual Studio 2017 Update 3
- TFS go offline consistently (15 votes)
To be fixed on Visual Studio Team Service (we found a service side fix)
- Can’t Check-In Changes in VSTS (27 votes)