Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Some features I would like to see in the ASP.Net “vNext”

I would also like to see a template for the MVP pattern.

There are so many apps using Web Forms, and most people I have talked to want to update the apps to use the MVC, which is not easy at all.. they want to do it to make it easier to write tests. By having a MVP for Web Forms, it will be easier for them to upgrade their apps and make it possible to write unit test etc.

I want the Cache object to use providers, so it's possible to use it with a distributed cache (for example Velocity) to enable it for Web Farms. Many developers are using the Session now to cache stuff in a Web Farm environment, but the Cache object is more powerful, but it stores the info InProc.

I want to make it possible on a TextBox level to turn off "HTML Validation" (ValidationRequest), not for the whole page.

Add a size limitation for the Session as default, several developers are adding Search results to the Session. I think it should be great with a limitation so developers need to increase the size of the Session object. That will probably make them rethink, and reduce the use of Sessions.

I want to see the runat="server" attribute removed from controls.

Add support for custom tags, where a tag is bound to a specific class, for example:

<my:CustomTag DataSource="<%= Model %>"/>

By letting us to add/create custom tags, we could easily create controls for the ASP.Net MVC Views and a custom tag solution can solve more than just creating controls.

Add better chrome support for WebParts, for example using templates. I created a solution for it a long time ago on my old blog: http://fredrik.nsquared2.com/viewpost.aspx?PostID=248, I think it will make several SharePoint WebParts developers happy ;)

What would you like to see in the next version of ASP.Net?

3 Comments

  • 1. An easier way to bundle/compress custom JavaScript and CSS for Release builds.
    Currently we have two options: put them all in Resource Files, and link in using the ScriptManager -- or, do it ourselves. I'm OK with the DIY option. But the Script Manager part stinks (because of all the other JavaScript it then forces on you)

    2. Page specific JavaScript files (*.jsx?). In my aspx file I can type (or any other page value) and get the value. But if my JavaScript gets too large I like to move it to a separate JavaScript file (also makes JavaScript unit testing possible). When I do that I loose the stuff.

  • Chris' #2 sounds good. I don´t want that ClientId stuff (I prefer to have control over my id's), but page specific javascripts sounds great.

    I would love to have something like this:
    http://vinkr.net/1750

  • In asp.net 4.0, you'll have full control of the IDs and how they're generated.

Comments have been disabled for this content.