509 votes11 comments · Visual Studio IDE » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
When the item was marked as completed, we have misunderstood the suggestion. Your suggestion is still valid, and on our backlogs. But we are not actively working on this.
Opening the suggestion again for you to upvote this one. Sorry for the confusion.
VSTS/TFS Program Manager
Please add this to Visual Studio "15"
185 votesunder review · 13 comments · Visual Studio IDE » Languages - C++ · Flag idea as inappropriate… · Admin →
Make it available via NuGet to
I wanted to update the status to make sure you know that we hear you. This isn’t straightforward to deliver for obvious reasons: Visual Studio installs a disparate variety of tools, runtimes and SDKs, many of which come from third parties or other parts of Microsoft. We recognize that developers would love to see something lighter and while we have nothing new to announce at this stage, we are spending a lot of time thinking about how we can improve Visual Studio installation.
Thanks for the feedback!
Tim Sneath | Visual Studio Team
Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to address this suggestion in a future release. Thanks for capturing the pain points you feel when stepping through multithreaded applications while debugging. We will be providing an update soon.
Additionally, I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread. If you have other breakpoints in your application and another thread hits one, then you will be debugging in the mixed thread state as described in this item.
Program Manager, Visual Studio
174 votes29 comments · Visual Studio Team Services » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
Thanks for a great suggestion!
A Visual Studio extension for Markdown is now available for free and can be downloaded here https://visualstudiogallery.msdn.microsoft.com/eaab33c3-437b-4918-8354-872dfe5d1bfe
This may be built in to Visual Studio in a future release.
Visual Studio Web Team
I wish this was available even for TFVC
We’ve begun work on this and are considering changing the default location for new projects to C:\\USERPROFILE\Source\repos. Would this be a reasonable change to address the problem of “clutter” in the Documents folder? This is currently the default for cloned repositories, so all projects would be in a singular default location.
As well, you still retain the option to change the default if you’d like.
Program Manager – VS IDE
Thank you for the feedback!
We’re currently investigating the potential to support C++ debugging with IntelliTrace. To help us better understand your needs, please take this short survey about C++ debugging with IntelliTrace, or email me at Deborah.Chen@microsoft.com to share your thoughts.
Survey link: https://aka.ms/cppintellitrace
1,052 votes36 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
Thank you all for voting on this suggestion. The team has heard you and is considering this request, possibly for a future release.
Deonhe – MSFT .NET Framework team