Expressions Trees are immutable objects, which makes them excelent in many caching scenarios, except for one big detail: They don't implement Equals or GetHashCode().
Considering the fact that they are immutable, I think it will be great if they implemented such methods, so they can easily be used as dictionary keys (for example).

Also, this is more compiler specific, but I think that Expressions generated inside a method, without any reference to local variables, should be implemented as static readonly, always returning the same instance instead of generating a new instance each time. After all, the expression is immutable, so there is no risk of threading issues.

Please enhance or create a new toolbar editor for Visual C++ that is on par with the one available in C#. It seems insane to have to still edit bitmaps outside of Visual Studio in order to get 24 bit colored buttons. I want to easily add buttons and set their bitmaps from a file of my choice just like I do with toolbars and image lists in C#.

Also, I think there is a bug in the current Visual C++ toolbar editor in VS2012 Update 2. If I right click on a button in the current editor and select delete, the button turns black and a new button is created. So, instead of deleting a button, I end up with an extra one PLUS one with a black bitmap! Clearly, the toolbar editor is not getting the attention that it needs.

We use scrum for our projects, but usually without tasks or other sub-items. So the current task-board is less helpful and we're looking at using the kanban-board instead.

In some cases we still do use sub-tasks though and we need those on the board that we use.

If there would be kanban-boards on the sprint level (another suggestion: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3939137-add-a-kanban-board-on-each-sprint-level-instead-o), only those would need to show the sub-items. The kanban-board on the product backlog level, would only need to show the requirement-category items as it does now.

And maybe the visibility of task-category items could be an option so you can turn them on/off.

TFS has no way to delete a project at the UI. If you have the authority to create a project then you should be able to delete the project.
Real World scenario: Source Control ended up in an unusable state with one project not checking in fully.
Had to make a new TFS project, a new local workspace and map the local directory to this New TFS project. So now the original TFS project is not connected to any local directories and I want to get rid of it. (No history etc worth keeping.)
Another scenario: Created a hello World project and practiced source control on it. Now I want to get rid of it.

I believe there is a command line prompt way of doing this within VS2012 but this seems tedious and opens possibility of deleting wrong project.

I am testing a winform app using (VS 2012 Update 2). There is a login for the app that takes quite a bit of time that I'd like to avoid for each test, so I am setting CloseOnPlaybackCleanup to false to keep the application open in between tests.

All tests within my Coded UI framework for the application inherit from a base class. Note that the ApplicationUnderTest.Launch and setting of CloseOnPlaybackCleanup to false are called within the MyTestInitialize of this base test class. Any given test may open mulitple windows depending on what it's testing, so within MyTestCleanup of that base class, I want to close all open forms except for the main application window so that the application is in a clean state for the next test and all that is open is the main application window.

Our goal is that each individual test case make a best effort to close all windows that it opened. However, in the case where the individual test case did not clean up the windows due to unexpected windows or test failure, I want the base class to clean up anything left.

My suggestion is Visual Studio to either close all forms except for the main application window in between tests when CloseOnPlaybackCleanup is false, or a good performing way to discover all open forms associated to the application, so that I can then loop through them and close them.