1 voteMatthieu Penant commented
There should be an option to filter out extensions that are not compatible in the current version too. It's useful to see which are not updated yet, but once it's done, it would make the navigation easier.
If it could be retrofitted in the VS2015 extension, it would be even better considering some of us will have to live with both versions side by side for some time.
289 votes15 comments · Visual Studio Team Services » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
This was archived by mistake. I’m sorry for the noise.
Program Manager, VSTS
We are planning to have a private preview of the VSTS Symbol service when the Visual Studio 2017 version 15.3 release. This will allow integrated authentication from Visual Studio to the VSTS Symbol Server.
With TFS 2017 and VSTS, you can see a history of changes for a build definition. You can select a previous version from that history and restore the definition to that version.
We are now beginning to look at how we can manage definitions entirely in source control so that you can use the same branching and policies for definitions as for the rest of your code.
1,009 votes65 comments · Visual Studio Team Services » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
We have a lot of investment taking place on our code review platform that will enable iterative code reviews, and we will initially bring that functionality to Git (via pull requests). Improving iterative code reviews for TFVC is still on our backlog, but it is not in our 6 month plan, so we are resetting the status.
1,173 votes71 comments · Visual Studio Team Services » Work Item Tracking · Flag idea as inappropriate… · Admin →
1,022 votesplanned · 63 comments · Visual Studio Team Services » CI (Build) · Flag idea as inappropriate… · Admin →
9 votesMatthieu Penant shared this idea ·
Hello everyone and thank you for the feedback. We are actively investigating ways to improve how Visual Studio handles project content. This suggestion falls into that category. Unfortunately, we will not be able to address this feedback for the Visual Studio 2015 release. We will update the community when our plans in this area have gained more clarity.
Visual Studio – VS IDE Project and Build Team
978 votes33 comments · Visual Studio Team Services » Work Item Tracking · Flag idea as inappropriate… · Admin →
Unfortunately we have had to make the decision to not bring the new Inheritance model to TFS on-prem with the next major release. It was a tough decision that we didn’t take lightly. The scope cuts that we had to make in order to deliver it to on-prem were just too painful, and would not give the User Experience we would be proud of.
We are still planning to bring it to our on-prem customers in a future release of TFS.
Sorry for not having a better answer.
VSTS/TFS Program Manager