Bake inversion of control into the framework and reduce the reliance on inheritance. This will allow greater extensibility and enable new scenarios. A good example of this is MVCTurbine (http://turbineproject.com) - rather than developers having to roll infrastructure themselves, they could hit the ground running with their IoC container of choice.

Add please more MONO support/compatibility

After some time certain parts of code i n a project end up not being used anymore and just waste screen estate. It would be handy if Visual Studio could detect this and warn you about it.

Spark is great but doesn't have a very good developer story inside VS. Having intellisense work on Spark views would be really great, not only code-wise but also for HTML and JS

When deploying a site, the previous version should continue to run. If the deployment fails, the site should continue to run on the previous version. If it succeeds, the switch should happen after publication is complete.

Today it's impossible to fully localize the view models / validations without using hacks or clutter the view models with the ErrorResourceName etc.

It would be a lot easier to handle localization if you created an extension point where one could register custom string providers.

Something like:

LocalizationStringProvider.Clear();
LocalizationStringProvider.Add(new MySqlProvider());

Full description: http://blog.gauffin.org/2013/01/better-support-for-localization-in-asp-net/

I can't stand the idea of having to install Visual Studio on a build server. MSTest should be standalone like NUnit (or any other test frameworks).

A simple user interface tool is needed to create and manage Users and Roles with ASP.NET Identity. Please port the ASP.NET Web Site Administration Tool ( http://www.asp.net/web-forms/tutorials/deployment/deploying-web-site-projects/users-and-roles-on-the-production-website-cs ) to work with the new ASP.NET Identity membership DB

I would love to use Script# similar to how Google Web Toolkit works. Your Javascript story is still pretty weak in terms of allowing us to easily make complicated AJAX applications.

Razor based pages need a design surface in the same way as ASP.Net Forms pages or straight HTML. This should support dropping of controls onto the page, dragging of margins and padding, and all the other features we have normally in design view.

As projects grow and transition from greenfield to brownfield projects .config files are getting more and more obsolete and dead stuff in them.

Do help me and show me what I delete of this.

The aspnet_compiler is slow to precompile web pages. We have a high end build server and the aspnet_compiler.exe runs and hardly uses in CPU or RAM.

Is there anything that can be done to speed up precompilation as it accounts for 50% of our total build time.

Please add a Report Viewer Control for MVC. Web Forms has one. Will not be able to completely move off of Web Forms until one is created.

We shouldn't have to download the votive stuff manually - WiX deserves the extra exposure that automatic inclusion would give it.

jQuery is great and all, but with a growing acceptance of two way binding from KnockoutJs, AngularJs, etc, sometimes it is just an overhead to add jQuery in order to use SignalR. Moreover, this brings a lot of problems when using ExtJs or other pure javascript UI libraries.

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