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.

Please extend MVC to support fluent API for validations.

Hi,

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

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 =)

I'd like to see better and easier localisation support. Something like what's used in Orchard.

Those of you wanting full OData support today can get it with much less code using WCF Data Services.

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

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

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?

Now is february, 24th, 2013. Could you please give us an update on your roadmap and future plans?

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

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.

Was support for Sass intentionally excluded, or will it be included alongside support for LESS?

output cache support for webapi is a real need. will you add this support?

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.

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?

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.

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?

Please add $count and $inlinecount to OData!

Would like to see output caching work with the web api

Please add $select to your OData implementation! It's critical for any scalable app to be able to support this with Web API.

Great!