Cleanup the Solution Explorer context menu
The Solution Explorer context menu is totally ridiculous. We pay lots of attention to the toolbar buttons but people (groups within MS) continue to through everything plus the kitchen sink into the context menu. Let's not put features in your face at the cost of good usability.
We re-ordered parts of the Solution Explorer project context menu in Visual Studio 2013 RC. You’ll find the ‘Add Reference’ and similar items in the ‘Add’ flyout and we’ve added a couple more flyouts to help reduce the root-level overload. Let us know what you think!
Barry Postma commented
@VisualStudioTeam A screenshot would be very welcome, can you post one here? :-)
Rudi Larno commented
I always hoped the customization would be easier (more drag and drop like it used to be VS2008)
And why not have an option that the MRU items 'float on top first' and after a while, the rest gets added (or is available via a fly-out)
Chris McGrath commented
@VisualStudioTeam - Can we have a screenshot of what it looks like in Visual Studio 2013?
Nickolay Kush commented
@Judah, that is better to spend 15 seconds (I dont believe in this ) in context menu(one click) then somewhere else (lots of clicks and tabs). It is customizable so fill free to remove all unused commands like I did with copy and paste.
@damianh, VS is awesome just learn how to use it, You could export your customization and put for every one and every one will have the same context menu like by 5 simple clicks to import.
P.S. Vote down 5000
Here, here, clean up that mess of a UX experience. I seriously stare at that for a good 15 seconds trying to find "set as default project", for example.
I removed nearly all buttons from the VS toolbar to have the same general set of 17 buttons from VS 2012 back to to the earliest VS net release.
Putting the rarely used context menu commands under Advanced is a good idea in 2012
Costomizable yes - but arbitrarily pruned I don't agree with.
After using VS for years, I don't think there are many items on the context menus I don't use semi-regularly and (most) of them get used multiple times every day,
Dennis Apter commented
Maybe it's time for introduce radial menu like Autodesk?
While everyone is saying "it's customizable!", the customize dialog is woeful. There must be > 100 entries for Cut, Copy, Paste, Rename all over the place. And it's all clicky-clickly-clicky. AND then you have to do this multiple times if you have >1 computer. :/
Clay Shannon commented
I disagree wholeheartedly; I pay virtually no attention to toolbar buttons, and the context menu in the Solution Explorer is my "go-to guy." Customizable? Fine; but don't remove anything just to get rid of "clutter" (you'd probably get rid of the things I use the most). An example of this is MS Word, which I find much more difficult to find what I want than formerly (such as Select All, etc.)
William Bosacker commented
I have to disagree with the blatant removal of any items, but I do agree that it should be customizable. There are way to many tasks that used to take only 2 clicks, that now take as many as 5 clicks, which makes absolutely no sense at all. Especially when they are tasks that I use all the time.
The bottom line is, if it's not going to be customizable, then leave it AS-IS.
Abel Pereira commented
Although I have no votes left I totally subscribe this topic. Solution context menu is so big it actually takes me time to find the item I am looking for. Yet, I suspect some of the items may have a residual usage and could be placed on a sub menu or simply removed.
Although I never enjoyed very must the [old] office approach of hiding items barely used, this might be a way to go. Anyway, this is an issue I have been noticed for a while and it's continually getting worst. Hope VS team do something regarding this.
I personally don't have a problem with long context menus but I think there is likely a better approach to let users decide how to use it.
I do have an issue with context menu options which get used a lot, like source control, but are suddenly part of a sub menu. Why the extra clicks?
The context menu, attached by Scott, has a build options.
It would be good to let the user choose if that only shows as toolbar button, only as context menu choices or both.
This setting could be added within the toolbar drop down which lets users add or remove buttons.
Wouter Vos commented
Could you give some ideas on what you want to remove? For me the context menu is fine, but I'm not a web programmer, which you seem to be. Also I almost never use the context menu. I'd downvote this if I could, but no downvotes allowed...
Will Grosett commented
Carey Payette commented
Chris McGrath commented
Just a reminder, Visual Studio has an excellent extension model. Somebody could write an extension to do this.
And for those who are saying there's the option to customise already - Have you actually tried to use it for context menus? It's completely unusable.
Totally agreed. +1