It would be nice, if you can select lines of code and collapse the code in the same manner as regions.
Longer project files will be more operable.
for example
Line
101
102
+ ...
205
206
207

Also it will be great, if you can select lines of code, mark it as comment, and can collapse/expand it in the same manner as regions.

It would be nice if "Find references" when the cursor is on the getter or setter of a property only found examples where the getter or setter is used. For example, I want to find everwhere where property X is set, but I do not wish to find the hundreds of places where the property is just read.

Ctrl-Shift-V is awesome for the clipboard ring, but when you pass the item you are after, you have to go all the way back round.

When using bookmarks in Visual Studio 2010, some key combinations cause bookmarks to get moved to a different line, making it somewhat pointless to use them if you make use of many of Visual Studio's key combinations (of which there are many). I would like to see the bookmarks stay with the line of code it was originally created on.

Provide the System.Configuration assembly reference by default in Visual Studio projects. This avoids the manual effort of having to include the assembly reference in each and every Visual Studio project that requires the use of a configuration file.

When my color settings are not what I want them to be I have to go to Tools -> Options -> Environment -> Fonts and Colors. There I have to find the Item I want to change. It is hard to find the item which item I'm interested in. While this items is already on my editor screen it would be great to change it there.

once a bookmark is created when code is entered above the location of the bookmark the bookmark no longer remains on the line number where it was created.

being able to drag the bookmark back to the line number where it was created would save many steps recreating the bookmark where it is actually needed.

<td class="tc3 " id="statusReason_@{@row.PayerStatusHistoryId}">...</td>

We should not need to force the @{@var} in order to just achieve @var.

Also, intellesense does almost never works.

Allow to change code formatter settings so that automatically formated code will meet the StyleCop formatting and ordering rules.

Support Edit.PrevousMethod in C#.

This command is available only in VB, not C#.

If the comman is available, it can be used in Quick Launch and a key assigned to it if desired.

We need a Refresh button inside "Find Results 1" and "Find Results 2" windows, so we can restart the same search with the same parameters (file types, match case and so son)

The design surface in VS2011 needs to support Razor pages to allow visual page design: the addition of controls, resizing of elements etc.

I hope that the code definition window have a text zoom function such a source code edit window.

1) Make describing syntax color coding as easy as text mate - a set of text files. **** - make it compatibile with text mate while you are at it. The current model works if you want to eat,live and breath VS extensibility - but that's just broken.
2) Make a chrome-free version of the editor. I want to launch the editor outside of VS to work on my files. And make this load time FAST.
3) Allow alternate rendering engines. And make it dirt simple. :)

Add exception's comments automatically when entering the two slashes "/ /" upon a method that throws one or more exceptions.

I use FindNextSelected all the time, but as soon as I use Find in Files to find something in my whole solution, the scope of every other Find operation changes to whole solution. This shouldn't happen. In-editor find and Find in Files should have different scopes, and FindNextSelected should use the in-editor scope, as it did in Visual Studio 2010