Has the menu & toolbar customization functionality in VS2010 been reduced?
I can't seem to be able to select an icon for an added command, nor set it to be icon-only. Previous versions of Visual Studio supported this functionality and even allowed the creation/editing of custom icons.
Is this something that has suffered as a result of the move to the WPF-authored UI or am I missing something?
Right-click the Quick Access Toolbar then select Customize the Quick Access Toolbar on the shortcut menu. Under Customize Quick Access Toolbar, select the command you want to move. Select the Move Up or Move Down arrow.
In Manage mode, click View | Toolbars and then select Customize. In Manage mode, click the drop-down arrow, located to the right of the Main toolbar or File List toolbar, and select Customize.
Add, remove, or move a toolbarOn the menu bar, choose Tools > Customize. The Customize dialog box opens. On the Toolbar tab, perform one of the following sets of steps: To add a toolbar, choose the New button, specify a name for the toolbar that you want to add, and then choose the OK button.
Customising existing toolbars and menus and creating new ones can help to provide your application with a clear and intuitive user interface. The following are all some examples of the things you can change or customise: 1) Remove controls that you do not use from the built-in toolbars.
Seems like this functionality was cut from Visual Studio 2010. This post has some info in the comments: Customizing Visual Studio 2010
Specifically - "Unfortunately assigning or editing icons to commands through Customize dialog is not possible in VS2010. It is one of the features got cut for lack of time. This is however something we'll consider adding back in next version."
The reply also has a longer explanation of a workaround.
As noted in the link mentioned in the answer from @Gordon Mackie JoanMiro, the REASON for the reduced functionality is that the VS Shell team migrated the entire UI (shell and command system) from Win32 to one based solely on WPF. This was a gargantuan task, I would imagine. However, a couple workarounds are now available:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With