The solutions I work with frequently have names longer than "Release" and "Debug", things like "UNICODE_Debug MT" or "MULTIBYTE_Release", etc. Unfortunately, there are very few pixels dedicated to this combobox in the toolbar, so only "UNICOD" is shown making it difficult to disambiguate and determine what configuration is selected.

I suggest you make a login screen so that every user has his/her files everywhere

http://www.youtube.com/watch?v=pWgaAJqJsG4

It would make it easier to switch between developing on laptop and desktop.

Problem: Lots of similarly named Projects eg ConsoleAppliation1001.
Which one is it? with that useful piece of code in.

If you add File Preview, (doesn't load the entire project. but launches essentially a ReadOnly Editor Window with just Colorised Syntax Highlighting of the code. (Eg. No Compiler Errors / Warnings)

Or incorporate the idea of VSQuickLook into the Start Screen.

http://www.dreamincode.net/forums/blog/217/entry-3004-project-vs-quick-look/

From time to time I think it would be interesting to write a few lines of code into a smartphone. Ideas can arise when you least expect it. Perhaps you're on the street, restaurant, park, friends house and the only thing you have to write your project is a paper (!?!) . A paper cant 'debug' codes and show syntax hint/error.

If you delete the preferences files (.suo and .user files), which happens when you checkout freshly from source control, the startup project is not set. Currently, VS10 chooses one for you but it is wrong most of the time. It should not choose any class library project. It should choose the following project:

(from p in projects
where p.IsRunnable
orderby p.Dependecies.Count() descending
select p).FirstOrDefault()

The project with the most dependencies is usually the right project. It is the main executable.

When building apps, project files can get long. Having the ability to nest files would be a great way to organize a project. Currently, this is accomplished by manually modifying the project file.

I need to change the default project namespace in project properties and do Search&Replace in all files already generated on startup every time I am starting a new project.

If namespace refactoring is not going to be available, at least allow us to set the namespace during creation of a new project.

It would be handy to see all custom targets and the order they are in.

Integrate CleanProject (http://code.msdn.microsoft.com/Clean-Cleans-Visual-Studio-a05bca4f/sourcecode?fileId=25377&pathId=701425930) into VS11. It's very helpful feature.

We need a update/service pack/MSI / or something compatibility package for SSIS projects developer in VS2008, or a less a view or preview of this projects and we testing this

Best Regards

It's bad when you checkout version from source control and have to follow a few more steps to make it work. The list of loaded/unloaded projects is not a solution user options!!! There should be another place for that info (and clearly not in binary format).

I can't tell you how many times a day I go to open a new project/solution and press Ctrl+O, navigate to the project file, press Enter and have it open the project as an XML document instead of as a project! Drives me nuts. Then I remember I have to use Ctrl+Shift+O to open the project. How about just consolidating it all as Ctrl+O and you can add a checkbox in the Open dialog for those very rare cases where you want to open a project as an XML document?

Especially in the context of mysite.visualstudio.com, it would be nice to have a project logo/icon/graphic to improve visibility and recognition.

When loading a VS2010 solution in VS11 beta it displays a dialog (in some cases) saying that a project needs to be upgraded and that you can choose not to load the project. But it doesn't provide any information as to why the project needs to be modified. Therefore you have no context to determine whether you should or shouldn't upgrade the project.

In Nant, it is possible to add a base path to an item group like:

<fileset basedir="${source.dir}\Database\Bin\">
<include name="1.sql" />
<include name="2.sql" />
<include name="3.sql" />
</fileset>

In MSBuild, I have to say something like:

<ItemGroup>
<File Include="$(BaseDir)\1.sql" />
<File Include="$(BaseDir)\2.sql" />
<File Include="$(BaseDir)\3.sql" />
</ItemGroup>

Can we have something similar like this in msbuild:

<ItemGroup BaseDir="$(SourceDir)\Database\Bin\">
<File Include="1.sql" />
<File Include="2.sql" />
<File Include="3.sql" />
</ItemGroup>

"Rebuild" and "Clean" need a seperator between them and "Build", or perhaps should be submenu options, or something. Anything that helps keep me from accidentally clicking "Rebuild" or "Clean" instead of "Build", blowing an hour of time.

The ability to give developers a customizable licence activation set of features! With mysql, sql or external database connection. Also making it possible to activate serial's and beta key's from online web apps made from coding languages such as php, perl, python etc.

Support to all Languages dynamically in single program e.g if we java with c in single program to make program efficient and fast to code. And there should be no libraries .
public class void//java code
{void main()//c/c++ code
{
}

}