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.

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(){...}");
}

We want better implementation of SimpleMembershipProvider that is not related to Sql server so we can use NoSql databases.
We also want implementation that is not that complex and that reference bunch of dlls (DotNetOAuth is very over complex library to do simple stuff)

For almost every public-facing web site, I have to write my own helpers in order to generate complete URLs instead of relative ones.

@Url.ActionLink("About") should return:
http://localhost:1234/Home/About
http://sitename.com/Home/About
https://sitename.com/Home/About
etc...

instead of:
/Home/About

It's described here in detail: http://stackoverflow.com/questions/10607301/mvc-poco-controllers-and-fluent-routes
I don't want to inherit from framework Controller class anymore!
I want to just specify routes with some rules, describing how to map requests to methods and parameters of my POCO controller class instance.

Currently you have to add a data annotation for max length to get the server-side validation to work, plus an attribute on the html helper function to get the max length attribute written out.

It *will* fire javascript on the client if the max length is exceeded, but the max length would never be exceeded to begin with if the correct attribute was written.

I don't think I need to explain that one. But just in case we have DropDownListFor, why there's no RadioButtonListFor?

Right now you can pass one model to View using @model syntax. But in many cases there is need to have multiple Forms on page and instead of making one big model that covers everything, or splitting that View into multiple Views it might make more sense to be able to pass your Model to BeginForm. Good example will be view which has both Login and Sign Up forms on the same page.

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.

CSLA framework does this today

Please enable SimpleMembership in MVC apps. Not everyone is moving to oAuth.

Produce a powerful Datagird. because now must of people must use a third-party control (like telerik, ...)

At present the Web API Method can be accessed using URI,
It would be nice if the Web API can be exposed using a WSDL /2, which could be referred in the project.

When localising an app in mvc3, it's pretty easy to localise a model by adding display tags and pointing them to a resource. The equivalent tags for an enum, description, does not support this. If it did, it would feel more consistent for a front end developer who could just call the enum with razor syntax, without knowing whether the field is a string or an enum or a (anything else that has a string implementation in a webpage.)

Please use TypeConverter in DefaultModelBinder, received from metadata for binding.
There are a lot of attributes for view managing. For example DisplayAttribute, but for data input managing there is only IModelBinder. It can be applied only for class and param, but not for property.
For instance, I have 2 classes with DateTime property. In first class I need DD-MM-YYYY format. In second – DD.MM.YYYY. How can I do this? With support of TypeConverterAttribute I could create 2 converter classes and apply TypeConverterAttribute for properties. But now I need to create my own mechanism.

Actually i can do this:

[OutputCache(Duration = 60, VaryByParam = "id")]
public ActionResult Index(string id)
...

think that could be interesting to have a way to specify a cache dependency to a file or maybe other objects..

for example:

[OutputCache(Duration = 60, VaryByParam = "id", Dependency("~/FileXpto.txt"))]
public ActionResult Index(string id)
...