The VSDBCMD tool is the most underrated and under-documented one available for database developers. I have a number of applications that are deployed with this tool, where VSDBCMD is bundled with my custom deployment utility. VSDBCMD is supported on XP through Windows 7, and supports SQL 2005 through SQL 2008 R2.

With the release of SQL Server Data Tools (SSDT), it seems that Microsoft is deprecating support for VSDBCMD.

I implore you to at the very least provide developers with an updated build of VSDBCMD so that it will support deployment to SQL2012 database servers. This will give developers enough of a window to migrate to SSDT by then.

My main reason for wanting this is that SSDT is not supported as a deployment tool on XP systems.

The VS 11 new project page is difficult to use using the keyboard / tabbing between the panes as the order is non-obvious from first glance. It feels like it goes left upper, down, however the filtering / sorting isn't obviously less important than the general project type (left side treeview). There's no obvious way to select either of the major panes without using the tab key on the keyboard. Moving from the treeview to the project type takes 6 tabs

It's rare if ever that I'd care to sort by reverse name.
The default ordering now that I look at it is really odd. Why is it like it is? Why not just always order by name? This allows for typeahead to just work.

Speaking of type-ahead, it's broken in the treeview, and acts like I have the Alt key pressed.

Keeping on the treeview. It's kind of a treeview, by an outer heading that I can back tab to. WTF? This doesn't change color when it's got keyboard focus. How do I realise that this is where my control is when it's selected?

As a sidenote, the nuget package manager gets a bunch of this wrong as well, though tab order is even worse.

I would like to have the ability to Customize WorkItemChangedEvent so when WI is changes, the mail notification will include also predefined customized fields in addition to the predefined core fields it currently supports.
Today, the following core fields are included in every notification mail: Team Project, Area, Iteration, Assigned To, State, Reason, Changed By and Changed Date.
Customize field is included in the mail only when it is changed, this is the default behaiver of the TFS.
We would like to have this field in all notification mails, even when not changed.
For example, the customized field for the Project Account: When getting mail notification on a change in a Bug WI, I want to know which is the account without the need to enter the system (required especially cause we all use mobile smartphones).

Sometime while debugging the debugger switch between 2 threads while we are stepping through the code. I think that when we are tracing code, it should never switch tread and trace the other one (except if a breakpoint is hit in that other thread code).

Some time, it happens that every step (F10) step one line of some other thread. Next F10 would then advance the current thread, Next one the other thread and it will continue to alternate on each step.

When it does happen, it is very annoying. Switch thread in the thread pane does not seems to help much. When this problem occurs, I don't really know how to avoid it.

It should be easy to select one thread to debug and let other thread either execute at full speed or be suspended (or suspended while the main thread is suspended).

When a solution has some C++ and some C# projects, it cause all sort of trouble with references or designer.

As an example if a C# DLL is used by a C++/CLI which is in turn used by another C# project (that has a reference to both of them since it uses item defined in C# DLL), then there would be a lot of problem caused by references.

A common problem is that the WinForms designer will often complain that the C++ DLL from which it uses some class cannot be loaded (even though it is compiled and up-to-date). This is very annoying as it won't always get fixed by recompiling the solution.

When compiling and linking we can sometimes see errors or warning caused by wrong reference. Why the IDE is not able to properly setup reference, intermediate paths and all that stuff so that it properly works 100% of the time?

By the way when such errors occurs we don't have much information to understand why it does happens. It look like a problem that version does not match but why.

In my case, there are also another C++/CLI project under the above C# project and then the application executable which is a C# project.

And speaking of projects, it should also be easy to create a project that would have some part compiled native in both 32 and 64 bits and some to IL and have a setup that would allows to select if we want to install the 32 or 64 bits application if the OS support both (and by the way if the 32 bit application is installed in such case, it should be marked as such if the application itself is managed).

References to C++ code is also a problem for Intellisence (and maybe for test projects... I haven't done them recently).

By the way, it also seems that in some situation it is impossible to add a reference to a C++/CLI project compiled in VS 11 Beta using Visual Studio 2010 toolset.

References should works properly whatever toolset we chose to use and if some configuration use one toolset (or some specific options for CLR), everything should works properly anyway.

Fix the problem that cause DLL to be sometime locked under VS 11 Beta. It often display that 10 retries were done but why the DLL is locked in the first place.
When this occurs, we might have to close and restart Visual Studio or worst have to close the session or computer.

When this problem occurs, we cannot clean the project neither delete the DLL from Windows Explorer. I'm not sure if the DLL will eventually be unlocked if I wait enough... but if it is the case the delay is far too long anyway.

And you'd like to know, my Antivirus is MSE so I expect that is is not the problem since it is from Microsoft.

By the way, if it does occurs, it might be a good idea to create and use a temporary DLL (and fixes references) so that we won't lost too much time because someone does not properly close the file (maybe the debugger).

Provide the ability to do a search of text WITHIN files stored in TFS Source Control in a manner similar to what was previously available through VSS and is also available through Sourcegear Vault 6 (which also uses SQL Server database storage similar to TFS).

"Find in Files - New for Vault 6, the find in files command allows searching for a string of text within text based files stored within the repository. You will be able to find what you want, when you want. As a file’s data will be indexed in its own database, searches will be more efficient than keeping or GETting files to disk and running recursive greps against those files."
http://sourcegear.com/preview/Vault6Preview2.html