Currently, DependencyResolver is only applicable to MVC. If it is moved outside System.Web.Mvc , It can be reused in webservice pipeline too. Enterprise library uses servicelocator which is another way of location services. If EntLib is used in MVC applications, there are two mechanisms exist and that makes code inconistent.

To do this in MVC 3 seems unnecessarily complex - http://www.scottschluer.com/2011/02/01/creating-a-routedata-instance-from-a-url/

Add webpart/portlet framework to ASP.MVC

Not only see "Object reference not set..." exception, but also see where is a problem.

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

1) Make ablility to define default value for properties inside of a complex models using DefaultValueAttribule just like for action method parameters.

2) Introduce following optional url generation mode: if actual model member value equals to its DefaultValue then do not render it as key-value inside query string, example:

public class FooModel
{
[DefaultValue(1)]
public int PageNumber { get; set; }
}

rendered as:

/foo?PageIndex=2

or

/foo

but not:

/foo?PageIndex=1

RequireHttps, if present on a controller method, redirects to use https, however, when going to other controller methods that do no have RequireHttps it still uses SSL. We would need RequireHttp, which should be the default. This would redirect back to non-ssl. Also needed would be a IgnoreProtocol (perhaps a better name) that would allow either http or https.

Currently the only way to locate a controller type based on a request context and controller name is to use ControllerFactory.CreateController.

It would be nice to be able to locate the controller type without having to run a full instantiation on the controller type just so you can GetType() it.

Controller activation was separated out of the ControllerFactory... but controller type resolution wasn't. Can we get that fixed?

When writing things like site maps or action link helpers (e.g., http://aspnet.uservoice.com/forums/41201-asp-net-mvc/suggestions/2078037-authorize-check-in-actionlink-helpers?ref=title ) it is necessary to locate a controller, an action on that controller, and then evaluate authorization.

This is currently really, really painful. It'd be nice to have a more supported mechanism.

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

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.

HttpContextBase was a nice addition, but reimplementing HttpContextBase in unit tests is time-consuming when a codebase takes advantage of several of its features such as Request and Server. Would like to see a nice HttpContextBase instance generator given some properties or arguments.

Suppose that we have a @RenderSection("ScriptsContent") in the _layout.cshtml file.

If i use "@section ScriptsContent" in a View and i also use the SAME section in a PartialView, i would like to have it cumulative.

So the @RenderSection("ScriptsContent") will render the one declared in the View + the one declared in the PartialView.

It will be very usefull when you want to have all your scripts at the bottom of you page and want to declare them here and there in your view and partial view.

The current implementation of returning a View is parameterised by View name its model and other stuff like Master page, etc. what if it is possible to resturn a View with the View name, controller name and Model with optionally specifiying if the model state should be preserved or not (for validation messages). That would be great.

I suggest you have new membership providers for enterprise applications. Many of the projects I work on require groups of users that follow the same role under an organization. As well as, for that organization only. Also I wish more of this custom profile information was stored in there own table, instead of in xml in a table.

Right now there are a number of difficulties in getting selectlists / dropdowns to simply work right. It's just not intuitive. The top two most-voted issues on CodePlex are both related:

http://aspnet.codeplex.com/workitem/7629
http://aspnet.codeplex.com/workitem/4932

Posted on 8/15/2011 at 5:17PM you can find a comment on the first of the above two desribing the pains and my suggested fix. I hope that's helpful.

You can also find ample instances of users having issues with selectlists on the MVC forums (on www.asp.net) and StackOverflow.

Sometimes you need to build interstates and sometimes you need to fix potholes. Please fix this pothole! :)