I'd like to maintain one big pool of test agents and evironments for both queuing tests from the VS IDE, and for built verification tests from VS 2010 Lab Management. Please allow me to consolidate these envrionments and use them more efficiently. Please also introduce a concept of load-balanced deployments for VS Lab Management (e.g., an envrionment that can take builds from multiple branches, or even better a pool or envrionments)

Get business types be able to store settings centrally, i.e. if you add a custom phone number type, you have to manually add it to each column where you use Phone.
When you add a new setting it should be stored is a way that allows all instances to use it or it should be optional.

Provide a prerequisites installer for Visual Studio 11 in a manner similar to SharePoint 2010. Therefore, if users want to install all of the prerequisites before installing the full version of Visual Studio 11, they can do so and therefore avoid the re-boots in the middle of the installation process. In addition, if all of the prerequisites have already been met, then the installation can simply proceed with the installation of Visual Studio 11 directly.

Regarding the dialogue at Menu: "Tools" / "Options...":
Why is the options dialogue not resizable? The dialogue box is very small, so you can't see as much as would be helpful. Many items would win if I could see more of the content.
Set a minimum fixed width, but allow us with big screens to use the available space - screen space is for free :-)

In VS11 the "Publish Web" dialog should maintain focus when opened with a hotkey. The dialog loses focus and requires additional steps to publish compared to vs2010.

I agree that double-clicking a test result should open the test source code, not the test result details, but it seems there is now no option to view the test result details. The section at the bottom of the Unit Test Explorer that shows the exception and stack trace when a failed test is selected is too small to be usable. Reinstate an option that allows you to view the full test results in a tabbed document like VS2010, including: exception details, stack trace, debug trace, console output, etc (see attached).

Let the team decide if it wants to further decompose a PBI or not. Small PBIs should appear on the task board alongside with regular tasks, that are used to decompose larger PBIs/Bugs.

Currently the method to disable TFS auto connect is a registry key. This would be more useful / visible to the user in the options dialog.

TFS Auto-Merge works pretty well for most files, but CSS it seems to have real trouble with. Virtually every time i try to merge my CSS it messes it up. Please imporve the CSS merging and make it more intelligent.

Have Color.FromName return Color.FromARGB(255,0,0,0) where the string that is passed to it is not recognised.

This would support Forms and controls which only support solid colors.

If I'm in a status meeting projecting current work items and/or bugs from a work-item query onto a screen, there is no way to increase the size of the list without dropping my screen resolution. I can find font size tweaks for virtually every other part of the UI, but not for work items.

ATM, the only deployment method that is available is ClickOnce. While this is mostly the best choice, we need to be able to change to a different deployment solutions.

Sometimes at our organization we need to dynamically change our references depending on what type of build we are making. As it is now Visual Studio doesn't have a means to assign conditional references in projects. (ie: If HomeEdition build reference basic security.dll. If enterprise version build reference extended security.dll)

Dynamically loading .net classes using reflection isn't always the answer when some classes have to be used extensively.

When activating Annotate View for a source file, then one can see what revisions changed what parts of the current code.

It would be useful to be able to right-click a code-part-revision and choose "Show Annotate View before this revision". It would then activate a new Annotate View base on the version history from just before the specified revision.