Usability studies have shown that both shape and color help to distinguis visual elements in a UI. The upcoming/current beta release of Visual Studio 2011 has removed color from the toolbars and from icons in e.g. the Solution Explorer.

Please make this optional so those of us that want a more accessible and user friendly IDE can have their cake and eat it too.

You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it's too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future.

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.

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

Support C++11 features

The new one is very confusing!!!

I think the old one was almost perfect so why did you change it??? I mean, you can add new options but why did you change the philosophy?

The most important problems I see with the new one:

- No way to have that window independent so it can be accessed easily and fast

- Difficult to see at first sight the files changed! (of course, the new “no color” interface is part of the problem...)

- Difficult to exclude changes! (in the old one it was so easy by clicking the checkbox...)

Change All CAPS Menu in VS RC to VS Beta format File Edit Instead of FILE EDIT. Ref (http://blogs.msdn.com/b/visualstudio/archive/2012/05/08/visual-studio-11-user-interface-updates-coming-in-rc.aspx )

Rename existing project in TFS

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

The 260 character limit on file paths really gets in the way of having a deeply-nested project hierarchy. It's only there as backwards compatibility with the old school APIs, and has no place in any sort of modern development environment.

We should be able to work with file paths of whatever size we want.

The mostly black & gray glyphs used in Visual Studio 2012 are very difficult to distinguish between. Familiar icons that we have known and used for years are now gone, and it takes (wastes!) a ton of time trying to find the right icon/command/object. Please bring back the tried-and-true, full-color icons that clearly represent each command/object and are easily identifiable.

Add "Create Unit Tests" menu option to automatically create unit test skeletons for methods and namespaces as it was in VS 2010!

I am amazed you've decided to remove Macros from Visual Studio. Not only are they useful for general programming, but they're a great way to be introduced to the Visual Studio APIs.

If you are unwilling to put in the development time towards them, please release the source code and let the community maintain it as an extension.

T4 is no longer just a tool used internally by VS, but is being increasingly used by developers for code generation. It would be great to have syntax highlighting, intellisense etc. out of the box.

I appreciate this is probably more of a Visual Studio feature request than an ASP.NET one, but as T4 is used a lot within ASP.NET projects, particularly MVC ones, I figure it's worth a mention.

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

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.

It takes too long to begin debugging an application. It also takes too much time stepping through code in debug mode.

Provide the ability to create build configuration dependencies such that the success of one build configuration can trigger another build configuration such as a successful build triggering the building of an installation package or a build configuration which deploys to a development or staging server. Other tools such as Cruise Control.Net and Jetbrains TeamCity already offer build configuration dependencies/build configuration triggering through various means, therefore, TFS Build should also provide this type of support.