Make code that uses the concurrency runtime interoperate with the CLR. Trying to circumvent the limitation using the PIMPL idiom does not work either.

SL5 (as well as WPF) support setting the Value of a Style Setter to a Binding but XAML Windows Store apps do not (maybe because it was based on a snapshot of SL4).

Basically the producs backlog and sprints should look like this picture attached. It can be customizeable, how many children, etc.

All we see now are the backlog. but for a quick overview, our team would like to see the tasks required to get there. Gives a bit better overview for a 2 (sofar) people team. But most importantly for new guys to see.

In Test Explorer groupping Tests by Namespace is not possible like in older versions of Visual Studio.

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.

Your Git-Support for the TF Service is great. But what a lot of us need is the same ability in the On-Premise version of TFS.

I know that this is sheduled for the next major version of TFS. But hey; who can wait so long for that Killer-Feature? :)

So please provide Git-Support in one of the following regular updates for TFS.

Microsoft is apparently about to eliminate the classic view of MSDN in favor of the poor low-contrast, pale, washed out 'lightweight' view. When you visit MSDN now you will see the following if you are viewing the CLASSIC view:

"This view of the MSDN and TechNet Libraries will be replaced soon with the Lightweight view. Try it now by clicking the Lightweight link above."

This is more of the same from Microsoft in reducing the developer experience to a shred of what it once was, and makes using MSDN as unpleasant as the grey theme of VS2012.

Add MS Office support into Visual Studio to create, edit documents saved in TFS. Would be helpful to review or edit specification documents from TFS itself.

In the team Explorer, Change Default State value of a selected Work Item to Associate instead of Resolve on Check In. In VS 2012, our team often closed the work item because Team explorer Automatically chooses Resolve instead of Associate in team Explorer. Its really Annoying. In most scenarios, the developer is going to associate lots of check ins for a task. they resolve the task only once , when the task is completed. so its better to make a default value as an associate instead of Resolve. or At least given an option to choose an default value. Thanks.

When looking at the Task Board tasks and master work items, it would be helpful to know the ID numbers of the items up front instead of having to open the tasks and master work items up.

Would like the ability to migrate TFS On-Premise to TFS Cloud Services. We have been using TFS for years now and want to keep our customizations and history.

It would be nice to have ability to write complex rule for work items field. In my scenerio I have custom field Due Date and I would like to set its value to "DateTime.Now.AddDays(7)". Currently I can only use COPY rule but it support only static value.

Here is full description: http://social.msdn.microsoft.com/Forums/en-US/tfsprocess/thread/806d8398-00c6-4cd8-8356-228eeaef63ab

We can´t valite business rules involving a color change in the UI. Ex, if the balance is negative, the color of textbox where you see the balance is red.

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.

If there is a long title of a work item which does not fit on a stickie on the board it will not show a visual marker like "..." as a reminder there is more text in the title than is showed.

On several other places in TFS this behaviour does seem to be in place. But still not on the work item titles on the board.