24 votes0 comments · Visual Studio Team Services » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
I would extend this to top-level class declarations as well.
616 votes10 comments · Visual Studio IDE » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
Please, make Visual Studio and component updates less intrusive. Preferably - silently update as much components, as possible.
This is a great idea! We completely understand how auto-switching SCC providers would help increase your productivity. Although we plan to make this available to you in the near future, we are still in the planning process and may reach out for your feedback as we start to define how tackle this problem. We will check back as soon as possible with any updates to this request. Allison Buchholtz-Au: VS Program Manager
I also desperately need this. But to others I just wanted to note, that if your source control plugin supports scc bindings, then source control should automatically change whenever you open solution.
So I'd like to have per-project, not per-solution.
While we don’t have concrete plans to share yet, I wanted to let you know that we recently started discussions about potentially supporting this scenario.
I’ll provide an update once I have more concrete information to share.
Visual Studio IDE Team
506 votesunder review · 15 comments · Visual Studio IDE » Languages - F# Tools · Flag idea as inappropriate… · Admin →
Also, for large projects it would be nice to group files in folders. Even without ordering this would be very good