The AllowHtml attribute is all or nothing. In many scenarios we want to be able to allow specific tags such as <b> or <br />. How about an overloaded AllowHtml - eg [AllowHtml(br,b,i,p)]

Better grids and paging/sorting options, column sort images, individual column header css.

Support for server side javascript file such like script.csjs or script vbjs which executes server side codes and outputs pure js so we can add anything we need like localized text

The Url property of the controller can not be mocked for unit testing.

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

Sending data between actions when you do post-redirect-get currently still involves using ad-hoc tempdata. Would be nice if this feature is built-in.

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!!!

Allow support for when using EditorFor that you can reference a template that is in a different area

Name attributes are the only required attribute for form fields.

Template helpers for form fields auto generate id values.

These ids can easily clash and it is a pain to fix it by changing the html prefix throughout your site.

There should be a setting for asp.net mvc that turns off auto generated ids.

it would be really usefull if you could add an attribute to the ViewModel (like DataAnnotation e.g. [Required]) and have MVC render an additional attribute or class value to the html control generated.

So as an example:

In the ViewModel....

[AddInputAttribute( Name="class", Value="BlueInputField")]
public string TextInput { get; set; }

lets MVC render the html as:

<input type="text" name="TextInput" class="BlueInputField">

You could then select fields using jQuery or display differently using css.

Also Attributes like :

[AddLabelAttribute( Name="foo", Value="Bar")]

could be used to modify the html code generated by LabelFor.

Extending the DropDownList to show the items grouped by a category

<select>
<option value="">[Please select an option]</option>
<optgroup label="Group 1">
<option value="1">Option 1</option>
<option value="2">Option 2</option>
</optgroup>
<optgroup label="Group 2">
<option value="3">Option 3</option>
<option value="4">Option 4</option>
</optgroup>
<optgroup label="Group 3">
<option value="5">Option 5</option>
<option value="6">Option 6</option>
</optgroup>
<optgroup label="Group 4">
<option value="7">Option 7</option>
<option value="8">Option 8</option>
</optgroup>
</select>

http://weblogs.asp.net/raduenuca/archive/2011/02/26/asp-net-mvc-extending-the-dropdownlist-to-show-the-items-grouped-by-a-category.aspx

in cs or .cshtml file you can get the localized string. For example: ViewRes.Welcome which will return the localized "welcome" text. It would be great if we can do it in any javascript file. Is it possible?

I need preview for my html markup

Extending Unobtrusive Validation to fire an event BeforeValidation and AfterValidation.... maybe similar to how the Ajax helpers work maybe just with JS... not sure

This way, when you need to manipulate any other elements on the page when an error occurs then the developer has the control

Design Views in MVC.As We Design Forms in ASP.NET WebForms.

Take a cue from FubuMVC and other frameworks to make ASP.NET MVC more flexible and easier to extend. Common extensibility stories, such as model metadata providers, should not require inheritance and should be composable. Add some reasonable default conventions, but make it trivial to override or extend them.

Donut Caching (output caching with substitutions). One method would be to have output caching on the action as we have now but where you can optionally not cache certain partials within the view - perhaps by using a new helper .e.g Html.SubstitutePartial

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 .

Decimal point consideration for diffrent culture. Datetime binding as well.