After viewing the relationships between methods while in the Solution Explore, I want to return to the default-view with a keyboard shortcut. Or just back a step without having to use the mouse.

Do some usability studies and discover that 3 dimensional, coloured shapes are easier for our eyes to pick out. This grey, and bland UI makes everything look the same.

I am a keyboard user in Visual Studio 2012 and it is annoying to open every file in the find result while selecting find result.

In VS2008 a list of errors would always appear at the bottom of the screen after a solution build in which errors were flagged. That was a good idea, but does not happen in my version of VS 11 Beta

In newly announced Android Studio exist one very cool feature - ability to show all screens with different language settings. In Visual Studio 2012 we have a very helpful / useful Device View. It would be amazing to have option to choose localization language to preview in XAML Designer. This way I will be able to adjust my UI or change my localization, without running tons of emulators.

Revision control based on pessimistic concurrency has been obsolete for years (to say nothing of non-distributed revision control). The lock icon for an untouched file looks really silly.

Instead, I would go with icons to indicate new files, changed files, and maybe deleted files (with the file name greyed out).

First, there is documented UX research showing that words written in all caps are ****** to read and recognize quickly. Please change the top menu bar from all caps back to typical capitalization! I find the menus so hard to read!
Second, I don't like the lack of color differentiation on the Solution Explorer.. Folders, Forms, Script files etc are all the same color, making it extremely hard to differentiate between them quickly. Again, use of color is a basic UX principle, why abandon it?

It will be good to scroll over tabs with opened in editor documents, will help to switch between documents that I want to see at the moment.

I use Undo/Redo quite a bit and find myself having to go through too many actions to see the meaningful changes. What are now usually separate actions should be automatically grouped into a single action.

Most Microsoft server products that we develop against now run in 64 bits. However the VS IDE is still only available as a 32 bit version.

Integrating the IDE to these server products, eg automating development tasks when targeting SharePoint, BizTalk etc, is now often unfeasible because the object models or PowerShell commands that you need to invoke won't run in a 32 bits process.

By eliminatig the 32/64 bit boundary (Wow64) between the IDE and MS Server products integration on 64 bit systems will be much easier.

I spent quite a while figuring out that Visual Studio 11 using temp folders to store information needed to load and execute projects was causing problems for me. Not only is this difficult to figure out, but it seems that there should be a simple fix.

In the new solution explorer, one can drill into files to the classes contained in the file and then drill further to see the properties and methods of the classes.

It would be nice if we could filter by access modifier, for classes as well as for fields. In other words, I'd like to see only the public interface of the class and have to deal with private and protected members for example.

In Solution Explorer, if a page is not expanded so that you see [+], then double-clicking the entry should open BOTH the .aspx and the code-behind (cs, vb, etc).

If the page is expanded then the present rules, opening just the object clicked, should continue to apply.