Visual Studio seems to be getting slower. Please focus on improving the performance and limiting the enormous load on the HDD

Allow Quick Watch and other Debug functions to work with Lambda expressions.

"Expression cannot contain lambda expressions" makes this powerful language feature second-class within the IDE.

Especially for data intensive applications being able to write Lambda expressions in the Quick Watch, Watch, Immediate Windows and debug evaluation is a must have.

Imporve x64 debugger so Edit and Contunue works when running on Windows x64 o/s

The silent majority of VB6 users did not ask for changes that came with .NET

We request Microsoft brings back classic Visual Basic as COM development is back with Windows 8.

David Platt wrote an excellent article about why classic VB still thrives:
http://msdn.microsoft.com/en-us/magazine/jj133828.aspx

Creating string fields with "Yes" and "No" (or "True" or "False", or "1" and "0") as allowed values, is a viable "workaround" for a Yes/No field - but still, a real checkbox control would make it even better.

btw: Checkboxes are a Windows control introduced from the very beginning (Windows 1 actually, I checked. ;)

Rename existing project in TFS

It is common to make a few mistakes, duplicates etc when entering a bunch of new work items or tasks. There is no easy way to delete the bad ones and try again.

I know it is possible to to do this from the comamnd line, but it is a pain and defeats the purpose of having a GUI. The end result is that poor items get left in the project because it is a pain in the *** to remove them and start over.

It would be great to have a RowTest attribute (like in NUnit) added to facilitate parameterized tests, like:

[RowTest]
[Row(10, 10, 100)]
Public void Add_MultipleValues_ReturnsSum(int x, int y, int expected) { … }

I want to able to see function return value in managed debugger just like unmanaged debuger (it has this feature from Visual Studio 6.0!).

The current editor's user experience is a barrier to process improvement through customization of of the template itself. The idea that an out of the box process template will satisfy all customer needs (or even one of the several shipped by MSFT) will be a limiting factor on meaningful and valuable implementations of the product.

To keep up with improving processes, there needs to be a migration path for existing templates to be upgraded to new templates. Some information in work items may be lost when mapping these to new work item types of the new templates, but this may well worth the benefits of moving to a newer process. Creating a new team project is not always feasible, especially if the source code versioning needs to be in place.

Currently, to get these features into a CI build, we have to pass a lot of MS Build properties around. Having gone through the trouble of creating my own templates to handle these features, it would be nice to see them included out of the box.

Support C++11 features

Currently F# IDE integration into visual studio does not have any refactoring support. It would be nice to at the very least be able to handle renaming.

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.

I am a regular user of TFS. Many bugs are resolved as duplicate of other bugs. Do we have a shortcut to directly open the master bug.
If not , this will be a good idea to do so.

When creating a work item query, you are given the option to select the iteration path for which the query is to return results for. It will be fantastic if a token was provided such as [Active Iteration] and you can specify the active iteration manually, or TFS calculating it via the Start/End dates

...for example, change an existing work item from an Issue to a Bug, etc.

Users less familiar with the system frequently enter work items using the wrong work item type. Currently, you can't fix these items.