Allow for Web Forms pages to contain multiple server-side forms rather than just one. This allows for much better accessibility and usability in the pages.

Make the Model-View-Presenter pattern a 1st class citizen in ASP.NET/Visual studio, to combine the testability of MVC with the benefits of the WebForm abstraction layer.

True Ajax UpdatePanel. Right now there is to much data sent and received

As per David Fowler's prototype, support for binding to other other control properties and properties on data objects using a WPF-like syntax (declarative) or from code-behind (imperative).

It would be a very great future to use Razor and html helpers even in an asp.net aspx project pages. ( not only in mvc project)

I am an enterprise web developer for a large corporation and we don't use MVC. My last job with another large corporation did not use MVC. I understand that MVC is the future, but MVP on WebForms is still a standard in many .Net shops. Can we get more content on how to do some of the coolness that's being explored in MVC in MVP. Where's the love, I'm tired of translating code and concepts from MVC to MVP :).

Provide a Web Forms Rules Engine for creating ASP.Net Web Forms that can be completely designed through a User Interface/GUI in a manner similar to InfoPath.

Separate Web Forms from .NET Framework so it can be updated more often like MVC.

It would be so nice to have a possibility to apply arbitrary transformations to text content of aspx/ascx files before compiling them. This will open a way for a lot of interesting code-generation techniques.

For example, it would allow for folks that don't like runat="server" not to write this attribute. Instead of this they would just be able to use a simple transformation that will add this attribute to any tag with a namespace prefix.

You guys have open sourced ASP.NET MVC, Web API, and Web Pages as well as Entity Framework. Please open source Web Forms as well.

I think the model binding proposed in the Visual Studio 11 Preview is a great feature, but I think it could be made MUCH more powerful. I would like to see strongly-typed controls be something more like:

<asp:SomeControl ID="SomeControl1" runat="server" RuntimeType="string" />

Where SomeControl would be defined as:

public class SomeControl<T> : Control { }

And in the generated code, the markup would translate to:

protected SomeControl<string> SomeControl1;

The basic gist is to add in a special property like runat="Server" that would allow you to specify the T in Control<T> or T1 and T2 in Control<T1, T2>.

Currently, when using model binding, we can utilize model state validation by adding data annotations to our models. This works nicely as model state errors can be displayed in the ValidationSummary control. This feature requires a round trip to the server, however. I would love to see this extended to include an option to generate client side validation based on the same data annotations.

the datagrid Features are quite ok, But the wizards and the generated HTML ist still the 2.0 stuff.
Webforms is still the fastest way to bring data to the browser. If you dont need full control or tests webforms should get some design improvements, html code optimizations and jquery Background refresh.

Current Auto Format option uses ugly in-line server control styling. How about changing this to use CSS classes and client-side CSS styles in a style-sheet instead.

The Data Bound Update method should accept IEnumerable<Item> to support editing multiple rows, e.g., a shopping cart.
A Data source should support rebinding to the data returned from the Update method to cater for more complex data bound scenarios, e.g., showing a confirmation screen.

http://aspnet.uservoice.com/forums/41233-visual-studio-performance-feedback/suggestions/2060551-better-sql-azure-deployment-support

When using the SessionPageStatePersister, the control state still travels up and down in the request and response. I do not understand why this would be. It just bloats both unnecessarily.

ASP.NET Dynamic Data QueryableFilterRepeter and DynamicFilter controls currently use Page.InitComplete logic to dynamically generate their content. This prevents you from re-using these controls on a custom filter template to generate filters for a related (parent or child) table. By the time the custom filter template is initialized the Page.InitComplete has already fired and the controls simply don't work.