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.

Elevating F# to a more equal footing with VB and C# for ASP.NET

Currently when I publish my site/app it stay's online. It would be better to drop an app_offline.htm during publishing so that my app doesn't behave in a funky fashion.

OpenID, ADFS, and other redirection-based login protocols don't fit the membership provider interface at all. Please add an interface that can be implemented by an OpenID library decently.

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

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.

I made a small test and on a standard ASP.NET page, just only with removing whitespaces and line breaks, page size decreased by %35-40. Lower page size means higher performance. There are solutions for it but all are based on server side dynamic solutions. But there is a simplier way. For ex. just clean it when it is published and generate dynamic controls accordingly. It won't any give runtime overhead and will only give performance.

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.

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).

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.

It would be helpful if they allowed you to add a html comment specialized in letting the designer know that a specific region is using a specific JavaScript file that represents the view model. That way when the designer can’t figure it out, we can override it to be very specific. This would be very similar to the design time XAML syntax you can use to tell it the data bind type.

In most case scenarios I'm uploading my website files using ftp and publishing tool is very uncomfortable.Meanwhile not all hosting companies are giving full access to their servers.
I remember in VS2005 there was an extension named Dispatch. It was very comfortable, right click, upload and file is on deployment server.
I think this can really save a lot of development time.

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/

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.

Compiling views on the webserver takes a lot of ressource, and during that time the application is slow to respond.
I would be great if we could publish compiled versions of our views. I know razorgenerator do this, but it's not native and we only want compile views for deployment, not when developing.

Thanks