This document lays out a roadmap for ASP.NET MVC, ASP.NET Web API, and ASP.NET Web Pages. This is a planning document, not a specification of what is to come. We hope to implement most or all of the features listed here, but there are no guarantees. Plans can change. You can help change them! Please visit the ASP.NET UserVoice site to provide feedback on our plans so that we have a better picture of what you want to see in the next release.

ASP.NET is a set of technology components for building web sites and services whether hosted locally or in the cloud. Developers can use the components to build sites and services they need to support their application. ASP.NET MVC, Web API and Web Pages are components built within the larger context of ASP.NET.

We just shipped ASP.NET and Web Tools 2013, MVC 5 Web API 2 and Web Pages 3. We are now working on a refresh build (MVC 5.1, Web API 2.1, and Web Pages 3.1) to address a large set of bug fixes and several feature enhancements.

MVC

Attribute Based Routing– Enhance extensibility and complete the parity between Web API and MVC attribute routing

HTML Helpers– We have gotten lots of feedback that the existing HTML Helpers for drop down lists, checkbox lists and radio button lists are hard to use. We plan to make improvements to these and also look at adding new helpers for Mobile applications that allow you to provide a badge in your application for native mobile applications that are available in application stores for devices.

Web API

Attribute Based Routing – Add extensibility and complete the parity work between MVC and Web API.

Error handling – We are adding support for consistent Error Handling (Internal server errors) and Error Logging throughout Web API. This will enable consistent diagnostics, and integration with other projects such as ELMAH.

Tooling

The main focus for tooling is to simplify the experience. This includes:

We are enhancing the scaffolding templates to support more EF and non EF scenario, as well as adding an OData scaffolders that doesn't rely on EF.

As always we invite you to provide feedback and ideas for future development. Plans can change. You can help change them! Please visit the ASP.NET UserVoice site to provide feedback on our plans so that we have a better picture of what you want to see in the next release.

 

Last edited Dec 6, 2013 at 5:27 PM by yishaigalatzer, version 51

Comments

artificer Oct 5, 2013 at 4:11 PM 
I consider Database.Open (Webmatrix.Data) and ASP.NET Web Pages 2 to be a simple and elegant way to teach newcomers about database access before getting into more complex ways of building a DAL.

I hope MS keeps supporting it.

amitraisharma Jul 23, 2013 at 3:06 PM 
Please extend MVC to support fluent API for validations.

Yustme Jun 26, 2013 at 9:58 PM 
Hi,

I'd like to see better support for localization. Especially for enums.

Rujaun May 5, 2013 at 6:26 PM 
Thanks for all the hard work! I'm really glad that you guys are trying to simplify the use of DropDownLists, Its a real pain in the ass to make it work, and not allot of helpful tutorials and info on it. And very smart move to integrate twitter bootstrap!

This is why I love to be a .net developer =)

RichardGarside Apr 19, 2013 at 2:05 PM 
I'd like to see better and easier localisation support. Something like what's used in Orchard.

jfattic Mar 25, 2013 at 8:32 PM 
Those of you wanting full OData support today can get it with much less code using WCF Data Services.

nikolawannabe Mar 25, 2013 at 6:03 PM 
"Web API with Security" Man, wish I would have known this 30 days ago, when we started building OAuth support for our WebAPI. Still, good to hear!

klabran Mar 25, 2013 at 5:27 PM 
I like what I'm seeing. A thought on using Bootstrap in the templates. I love it but some may desire another framework and/or none at all depending on the project's need, size, team, etc.... Flexibility in this situation might be best. Could you offer a bootstrap and non template version. Perhaps you can make it part of the project creation dialog like unit tests are? That would save on project type pollution while still allowing for extensions for another to add in framework Y....

leriksen71 Feb 28, 2013 at 1:01 PM 
Nice direction guys. The new ODATA work looks promising. Any possibility for some kind of discovery service and client/proxy generation in the future now that most of the foundation is laid?

lafi Feb 24, 2013 at 2:09 PM 
Now is february, 24th, 2013. Could you please give us an update on your roadmap and future plans?

dlaub Dec 18, 2012 at 5:37 PM 
The PowerPoint deck for the SPA Template talks about a December release - but it is already mid-December and I've seen no blog posts, etc. indicating when this template will really be available - can anybody comment on this? Thanks

VictorWoo Nov 8, 2012 at 1:21 AM 
There is a set of js libraries that suitable for ASP.NET SPA. Such as:
knockout.js VS backbone.js
sammy.js VS nav/history.js
...
I think they cost much time to study.
Before release the next generation of asp.net (SPA), will you please brief us on which libraries will be chosen in the next release? So we can prepare ahead of schedule. That could be great help.
Thanks.

corydeppen Oct 9, 2012 at 10:37 PM 
Was support for Sass intentionally excluded, or will it be included alongside support for LESS?

msusur Oct 9, 2012 at 4:53 AM 
output cache support for webapi is a real need. will you add this support?

scothu Oct 4, 2012 at 3:56 PM 
joshuadavidlee, moving forward we plan to focus on existing client side libraries and enabling the authors of those to support them in our templates. As a result we do not plan to update Upshot.js. Upshot.js will remain I the source repository for people that want to use that code base.

joshuadavidlee Oct 4, 2012 at 2:15 PM 
Earlier this year the Beta version of Visual Studio 2012 included a template that was designed for building “single page applications” using a new library called Upshot.js and a special Web API-based DataController that provided support for insert, update, and delete operations using the unit of work pattern with transaction support.
-------------------------------------------------------------------------------------------------------

And is this the plan in the future? You will continue to develop upshot js and the new data controller?
This will be the guidance going forward?

jeffyjones Aug 25, 2012 at 3:18 AM 
Probably a good time to update this now that you've had RTW. I see bugs assigned to "vNext" and "OOB" but those aren't very meaningful.

camelinckx Jun 28, 2012 at 5:39 PM 
Hi, great stuff & progress!
Is there a timeframe for MVC 4 to be fully released, what is your advice if starting a new project with a dev cycle of 6 months, go MVC 3 or MVC 4 RC?

cime3d May 25, 2012 at 10:00 PM 
Please add $count and $inlinecount to OData!

breynolds73 May 4, 2012 at 3:10 PM 
Would like to see output caching work with the web api

Geminiman Apr 9, 2012 at 4:15 PM 
Please add $select to your OData implementation! It's critical for any scalable app to be able to support this with Web API.

venjiang Mar 31, 2012 at 1:52 PM 
Great!