Please fix this one: http://support.microsoft.com/kb/2816241

I don't know, why you restrict all EF 6 alpha/beta testers/users - I think the public part of the EF API the scaffolding use is already unchanged.

Support creating extension methods with the @helper razor syntax, inside the APP_CODE folder.

This could be very useful, when creating html helpers, like the following code:

@helper ExtensionMethod(this HtmlHelper html, string data, string action)
{
<text>
<div>@data</div>
should I want to use Html here it is fine:
@html.ActionLink("Link text", action)
should I want to use Url here...
@{var url = new UrlHelper(html.ViewContext.RequestContext)}
@url.Action(action)
</text>
}

And be called inside any other view like this:

@Html.ExtensionMethod("Some text", "MyAction")

That'd be awesome! An easy way to make Html helpers!!!

It will be nice to have a fully supported and secure way to use forms and windows authentication in the same project. For example let's say that the project has three areas two of which can be managed using windows authentication but one of them can use forms connected to a custom database. In such way the app can support internal users and external users without having to deploy to separate apps.

There is a serious flaw with how the unobtrusive library works. A user can't do the following api call because it just doesn't work.

I'm not the only one who has had problems with this....

$.validator.setDefaults({ onkeyup: false });
http://www.tigraine.at/2011/08/26/jquery-validate-and-microsofts-unobtrusive-validation-dont-play-well-together/

http://stackoverflow.com/questions/8022695/asp-net-mvc-3-jquery-validation-disable-unobtrusive-onkeyup

http://stackoverflow.com/questions/5487139/how-can-i-customize-the-unobtrusive-validation-in-asp-net-mvc-3-to-match-my-styl

Add responsive design templates with mobile platforms please

While bundling and minification at run time is great, it is also useful at build time. For example, if you are creating a javascript library and want to provide a minified version, it would be very convenient to have an MSBuild task that creates a minified bundle.

For writing distributed database / (multi-master) database applications and/or integrating with other systems, being forced to use an INT for UserID is a killer. Please bring back support for uniqueidentifiers as the UserID and update SimpleMembership to support them, or enable a simple way to override via a provider model.

E.g., DefaultModelBinder catches all exceptions. If you mock a model that is bound and the model has IoC, DefaultModelBinder will catch also MockException (which inherits form System.Exception) therefore you can't mock it. What a shame from a framework that proudly says it supports testing.

I have to provide membership in an MVC web app to a Microsoft Dynamics CRM back end. CRM uses Guids as entity keys. The new simple provider forces the use of ints. Your old membership providers use Guids. Why not use generics so you can use any data type as key.

Refactor the existing controller base class or implement an alternative implementation of the controller base class that does not depend on the httpcontext.. like the web api controller .

It should be possible to create bundles during runtime. It's not always possible to know beforehand what scripts/styles pages need. Or it's not practical to create many combinations of scripts/styles.

E.g

~/Views/Shared/_Layout.cshtml
@{
RegisterScript("~/jquery.js");
RegisterScript("~/bootstrap.js");
}

~/Areas/Admin/Views/Shared/_Layout.cshtml
@{
Layout = "~/Views/Shared/_Layout.cshtml";
RegisterScript("~/jquery-ui.js")
}

~/Areas/Admin/Views/Posts/Edit.cshtml
@{
Layout = "~/Areas/Admin/Views/Shared/_Layout.cshtml";
RegisterScript("~/post-edit.js");
RegisterScriptCode("function Foo(){...}");
}

See for example this post by Hanselman http://www.hanselman.com/blog/ABackToBasicsCaseStudyImplementingHTTPFileUploadWithASPNETMVCIncludingTestsAndMocks.aspx that shows how troublesome the HttpContext is for testing.

The problem is that you have to stub several layers even if you only want to set a fake value for User for example. It would be great of this could be simplified so that it was possible to Mock/Fake only the properties/objects we need for that test.

This ModelMetadataProvider for Enums allows binding to dropdowns: http://geekswithblogs.net/nharrison/archive/2013/01/16/simple-way-to-bind-an-enum-to-a-dropdownlist-in.aspx

This would be pretty useful.

A strong part of MVC is its extensibility points. However, if you use an IoC/DI container, there is currently no way to populate its dependencies (similar to how you would a controller via the ControllerFactory).

Imeplement HTML5 Form Validations elements in MVC HTML Helpers and Web form Input controls

CORS is becoming more popular and should be fully supported in the ASP.NET stack.

I'm currently using ThinkTecture's IdentityModel package https://github.com/thinktecture/Thinktecture.IdentityModel.45 which recently added a CORS module for MVC and WebAPI, but it currently doesn't work if you have MVC controllers and WebAPI controllers setup in the same project.

Open source the project templates or move them to nuget packages, but let the community fork them or extend them or make it easier to get into the new project dialog... its holding us back.