Currently it is no supported. Please support FTP publish with MSBuild command.

Writing a HTML page with actual content on it (such as a rule sheet for a game) feels cumbersome and slow with having to enter tags manually.
I fully understand the separation between Views and Controllers; but still, these pages are basically HTML and a WYSIWYG designer can make work with these a lot more productive.

The ability to do Russian Doll Caching like you can in Rails.

I could see jQuery UI and Modernizer support in asp.net web application project. Meanwhile we are looking more rich UI building blocks like Twitter Bootstrapper. Something like http://addyosmani.github.io/jquery-ui-bootstrap/index.html, which works with jQuery

It would be really cool if the BundleResponse class was able to return binary content instead of just text content. This way it would be possible to create image bundles (sprites).

while knockoutjs is a nice databinding library, angularjs is a framework providing ioc and html extensibilty in a way the standart html dom will look alike in future standarts. intellisense support for directives and services would be cool.

This is the first customisation I do when I install a VS. I know it's already taken by 'select word' or something equally obscure, but consistency across apps is really really useful. For me it's one of the basics, like ctrl+Z/X/C/V/S/P etc.

I like to unit test a lot of my code, but hate mocking HttpContextBase just do to the horror of using something like Moq. It would be great to have a part of ASP.Net that was dedicated to unit testing and had built it classes that made it super simple to create mocks without heavy setup in my tests.

Also just make everything virtual in ASP.Net so we can override any public behavior (maybe not as possible).

Allow Visual Studio to insert images as part of the comments to the codes such as #region #endregion

Currently there is a trend back to moving towards having static content being generated during a build process. It would be interesting if either by extension or by a plugin to be able to generate static content using the layout and views during a build.

Implement possibility for PageInspector to store passwords like regular browsers do

Currently the <text> placeholder element assumes HTML content in Visual Studio formatting.
The addition of attributes (namely, "type" for Content-Type) to control Visual Studio's parser/formatter in these blocks would be quite useful for templating non-HTML content in template methods.

For example:

@{ object template = @<text type="text/css">
.foo { background-image: url("foo.png"); }
.bar { background-image: url("bar.png"); }
</text>; }

The type attribute in this case would enforce formatting of the template contents as CSS.

Adding these tags during resource generation causes problems for sites that do their own culture detection and setting. These settings override any previous set settings in code, and is a pain to remember to remove them when resources are generated. Alternatively, a setting other than "auto" like "none" so that the wizard would leave them alone and not set them again would be acceptable.

Current HttpReqeust, its abstraction interfaces and default implmentation are ugly. And they are still very hard to mock.

Currently it is impossible to get the wizard to generate resources (or the meta:resource attribute) for usercontrols. If you manually placed in the resource location, and manually placing a meta:resource attribute on the usercontrol, it works just fine. The wizard should treat usercontrols the same as the built-in asp.net controls in this regard.

There is a set of js libraries that is suitable for ASP.NET SPA. Such as:
knockout.js VS backbone.js
sammy.js VS nav/history.js
...
I think they cost much time to study.
Before release the next generation of asp.net (SPA), will you please brief us on which libraries will be chosen in the next release? So we can prepare ahead of schedule. That could be great help.
Thanks.

I would be nice to be able to upload a file as part of a model to Web API like we currently can on MVC. Web API doesn't accept HttpPostedFileBase as a field type like MVC does.