In for instance a C# project, if we show the properties of a referenced assembly, the properties list has the element "Version" which currently displays the AssemblyVersion. This element should be renamed "Assembly Version" for clarity. Also, a new element "Assembly File Version" should be added.

The motivation for this is that some third party components keep the assembly version constant (i.e. contract version) between minor releases, to reduce need for recompilation of dependent code. Such minor releases will still increase the assembly file version, so that it's possible to distinguish them. Only showing the assembly version in the VS GUI is confusing to the users (as they think they are somehow not getting the correct version) and might lead to bug reports that target the wrong version).

The namespace for new files created are automatically determined by the folder structure.
This often creates a problem if you wish to make a logical group of files (by placing them in a folder) that is not supposed to be a new namespace.
Creating the folder and moving the files is not a problem, but the trouble starts as soon as someone uses 'add class' on the folder.
Now the new file does not sit in the same namespace as the other files in the folder.

One example would be to use a folder to store partials of a big class:
[=>Folder root<=]
MyBigClass
[=>MyBigClassPartials<=]
MyBigClass_SetUp
MyBigClass_Update
MyBigClass_OtherStuff

it would be nice if I could assign [=>MyBigClassPartials<=] to the same namespace as the root,
So that new files end up in the correct namespace.

When opening a solution all projects are expanded by default. This quickly makes you loose oversight of your solution structure.

1. It would be handy if there would be a way to expand/collapse the solution's children, perhaps even by solution folder, single folder, or project.

2. Remember state after closing and reopening Visual Studio.

Additional comments from a merged suggestion:
In all the versions of VS so far, the default behavior when opening a Solution the first time is to open it with all the nodes and items expanded in Solution Explorer. This is not an issue until you start working with an Enterprise solution that has 50+ projects in it. I've spent time after initially-opening a large solution (for example because it has been copied to a new branch, or perhaps copied into a sandbox area) painstakingly closing every node so I can look at the list of projects in the Explorer in an intelligible fashion.

There are add-ins like ReSharper that give you a right-click Collapse All action - my client doesn't have such an add-in available. There are ways to provide yourself such an action by creating a macro. I'd like Visual Studio to provide this as an action, or better yet - provide an option that will change the default behavior of Visual Studio to instead, on the first time a solution is opened, to pre-collapse all the nodes in Solution Explorer.

Create a way to rename a project folder. This is closely related to http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2517011-enable-project-renaming- and http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3054944-rename-the-project-folder-when-renaming-a-project

I would like a way where I can change a folder name and optionally filenames: Project -> right click -> rename folder and files... -> give a new name, select folder, output filename or both ->
* Visual Studio updates name of the the solutiondirectory
* Visual Studio updates the solution to point at the new directory
* Visual Studio updates references of other projects to this project to the new directory
* Visual Studio updates the project to reflect the new output file name
* Visual Studio cleans the old files from the output dir if present

Extra brownie points for optionally integrating this in the rename project functionality (update output file name and directory to NEWNAME? <yes> <no>)

Double extra brownie points for a 'search for references to this directory from other tools': text-based search for all files not in obj or bin dirs in all folders under the solution dir that contain the old filename, and ask if the old directory name should be replaced with the new one, or if you want to open the files and edit them manually.

I really like being able to customize the toolbars with the commands I want (so please don't replace them with a 'fixed' ribbon!) but on older visual studio versions there was more flexibility in the customisation. On modern screens which are 16x9 there is a lack of vertical space but plenty of horizontal space. Toolbars across the top of the window use that valuable vertical space that could be showing lines of code, if I could run the toolbars down the left or right edges (as I do for the Windows Taskbar) I could reclaim that code space again, like I used to be able to do. Since they're now WPF based the rotation could work really well, with even the combo boxes properly rotated (as long as the dropdown part gets rotated back again!)

I also used to be able to mix toolbar buttons into the menu strip, again reclaiming otherwise wasted screen space and allowing for more code to be displayed.