Visual Studio IDE
Welcome to the Visual Studio UserVoice site. Let us know what you would like to see in future versions of the Visual Studio suite of products. This site is for suggestions and ideas. If you need to file a bug, you can visit our Developer Community website to get started.
NOTE: The Applications Insights forum has moved to the Azure feedback site.
For suggestions for improvements to other developer products, see these sites:
- Visual Studio Team Services (UserVoice)
- Visual Studio Code (GitHub)
- Azure Application Insights (UserVoice)
- Visual Studio Documentation (UserVoice)
- TypeScript (GitHub)
- NuGet (GitHub)
- Windows APIs and developer features (UserVoice)
- Microsoft Edge (UserVoice)
- MSBuild (GitHub)
- Xamarin (UserVoice)
We look forward to hearing from you!
- The Visual Studio Team
Terms of Service and Privacy Policy
-
Provide Stash support in visual studio tools for Git
There's no way i can stash my changes in Visual studio tools for git or any third party Git tools like mSysGit. Its great to support it.
1,832 votesWe are excited to let you know that we are working on this suggestion. We expect to release this feature early next year.
Kayla Ngan
Program Manager -
Allow multiple Git repositories to be active at once
This description has been modified by the admin.
This request is to have VS allow more than one Git repository be active at once. By allowing multiple repositories to be active at once, one can work with a solution that spans multiple repositories and also view histories and files of a submodule and parent repo at the same time.
1,452 votes -
Visual Studio Tools for Git Extension (Microsoft Git Provider) integration with Source Control Explorer window
The major feature that is still missing from the Microsoft Git Provider is to integrate it with the Source Control Explorer window to provide a full featured Git repository UI that will rival third party tools in it's feature set.
A great example of the ideal functionality is the Git Extensions main user interface. It allows changing repositories and branches, stashing changes, committing code and push/pull operations. It also provides a great visual diagram showing the commit history for the selected repository and where each branch (local and origin) is in relation to the head. It also allows you to…
418 votesWhen 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.
Ewald Hofman
VSTS/TFS Program Manager -
Provide the option to disable Git publish in visual studio status bar.
After the latest update (2) there is a new Publish button in the bottom right of the IDE. Doesn't state what it does, and even though TFVC is used it still creates a GIT repository on right click. Please provide an option to disable that button and please don't make my source control choices for me.
284 votes -
Squash commits in Git using Visual Studio
It would be nice, if we can combine (squash) multiple commits directly from Visual Studio.
250 votes -
Support patch adding in Visual Studio Tools for Git
Patch adding allows to stage only parts of a file (hunks), not an entire file.
The command line equivalent is the command "git add --patch"For example if you edit a file on line 20 and make another change on line 40 and now you want to split this changes into two separate commits because they are unrelated to each other you can do this by patch adding the file. It would be nice to have this functionality available inside of Visual Studio.
The same funcionality could be used to automatically include the changed parts of the csproj file when…
234 votes -
Move a file in TFS, which is dragged from on project to another instead of remove and add it
Until now, Visual Studio removes and adds a file in the TFS if it get traged/moved between different projects. Visual Studio should move the file instead to prevent the CC history.
The same could also be used for cut & paste a file.232 votesAs explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
Ewald Hofman
-
Enable "compare shelved file with local edits"
If you are interacting with a file in a shelveset, you get 3 options to compare the file in the shelveset to:
1. Compare with Unmodified Version: shelved file vs. version last gotten in the workspace that made the shelf
2. Compare with Workspace Version: shelved file vs. version last gotten in the local workspace (but without any local changes)
3. Compare with Latest Version: shelved file vs. latest version in TFS
*** I frequently want this fourth option, which is notably absent ***
4. Compare with local Version: shelved file vs. version last gotten in the local workspace (including…
226 votes -
SoapUI integrated with TFS
Please, integrate Visual Studio with SoapUI and also create plugin for Eclipse to integrated TFS with SoapUi perspective.
Thank you,
Rick212 votes -
Add context menu item in solution explorer to open Source Control Explorer showing selected file
When you right-click in VS 2010 Solution Explorer it would be great to have a shortcut there that opens up Source Control Explorer immediately showing the selected file.
Currently a user is required to open Source Control Explorer and manually expand (and know) all the folders in the path to get to the desired location.
198 votesAs explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
Ewald Hofman
-
Add TFS "Find by status" and "Find by wildcard" reports
Add "Find by status" and "Find by wildcard" TFS power tools 2015 report into Visual Studio 2017 IDE
192 votes -
Add git support for subtree add, push and pull
Git subtrees are a popular way of including code from a remote repo into a project repo. They have advantages over git submodules.
Visual Studio's git features need to support adding and managing push, pull and merges from subtrees.
The only way to use git subtrees presently is from the command line :
e.g.
Add a subtree (as a remote)
git remote add shared ssh://git@bitbucket.org/xyz/shared.git
git subtree add --prefix=path/to/code --squash shared masterPulling upstream changes
git subtree pull --prefix=path/to/code --squash shared masterPushing changes to the upstream repository
git subtree push --prefix=path/to/code --squash shared master188 votes -
Add more columns to Source Control Explorer
Source Control Explorer list only fice columns (Name, Pending Change, User, Latet and Last Check-in).
Please add more columns, like Last Modified Date, History Present, etc. that will allow us to see the last modifeid date of the file and not just the date when the file was checked in to source control.
The excellent example is, when you move the files/folders around within Source Control, you are forced to check in the changes, which is every file in the project. Resuling into the same check in date for all files and folders within the project. Now I have to…138 votesAs explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
Ewald Hofman
-
Allow "Compare working copy to historical version" version in TFS GIT 2015
Allow "Compare working copy to historical version" version in TFS GIT 2015
http://stackoverflow.com/q/34123687/30225
When I pull up the history of the file I can compare that version with another version listed in the history by selecting both and doing a "Compare", or I can compare a historical version and its changes wrt to its previous version by selecting "Compare to Previous".
However, there isn’t a command that will let me compare a historical version in the history list to the currently edited version on disk.
This was one of the best features of TFSVC and I would be good to…134 votes -
Add a "bug" annotation to feature cards on the features backlog board
When viewing the feature backlog board, a user is able to see a "Product Backlog Items" annotation, which can be dropped down to view a list of all PBIs. This list does not include bug items. It is also not possible to enable an annotation for bugs.
It is possible to enable multiple annotations at once for PBIs themselves, which can have both tasks and tests.
Please enable a "Bugs" annotation for features.
131 votes -
Don't auto enable the Git Source Control Plugin
Our development team (and every other team I've been on) hates the Git plugin for visual studio. We find it cumbersome compared to third-party tools or the command line interface. And it is a performance nightmare, especially with large repositories. This wouldn't be an issue if we could just disable the git plugin by setting it to none in the source control options menu. However, Visual Studio will ALWAYS reenable it if it detects a git repository in the directory of the solution.
We've resorted to regedit-ing to disable it.
If someone wants to turn off functionality, they should be…
116 votes -
Be able to review Pull Requests in the Team Explorer window
I would like to be able to review pull requests created in TFS 2015 on Premise. The review should consist of a code review tool that allows me to make comments similar to the way that it works with TFVC when using GIT.
111 votes -
Bookmarks for TFS Source Control explorer
New option in Visual Studio TFS source control explorer to create bookmarks of source location paths
105 votes -
Make Git Code Reviews more like TFS Code Reviews
Currently, the user experience for a Code Review in TFS vs a Code Review in Git differ like night and day with the former TFS Code Review process being infinitely more user friendly and intuitive than the comparable Git Code Review process.
https://www.visualstudio.com/en-us/docs/tfvc/get-code-reviewed-vs
https://www.visualstudio.com/en-us/docs/git/tutorial/pullrequestIdeally, the user experience should be the same within Visual Studio should be IDENTICAL in terms of features regardless of whether the development team is using Git or TFS source control.
104 votes -
Improvement for Find Shelveset section.
I propose add combobox instead of textbox in "Find Shelvesets" section. Combo should contain team member names or at least last input values.
Reason: it is not comfortable to look for shelvesets of another team members as you need to know how them names are spelled.89 votes
- Don't see your idea?