[Display(Prompt = "uname@company.com"), Required(ErrorMessage="Email required")]
public string Email { get; set; }

Am I missing something? I'm running Visual Studio 11beta. How come the Prompt attribute doesn't do anything? Shouldn't it put an HTML5 placeholder in? If not, do you have HTML Helper code we can use in the meantime?

What happens to WCF Data Services? Will they be dropped in favor of Web API ?

I like mobile device switching and device specific views! ALso glad to hear you are using the new features of TP

<a href="http://www.getfitsandiego.com/san-diego-boot-camp.html">San Diego Boot Camp</a>

Release date? Project pending decision to build on Web API or not...

"ONE ASP.NET" ????
Does that means I can have in the same app mixed/hybrid MVC + ASPX(WebForms) that really work easily?
A way to reuse UserControls in MVC? etc

Hi, do you have some kind of release date when the release of MVC 4 Release Candidate?

It would be nice if there was better support for themes (not just switching out the css) - maybe something like Orchard?

I like your theme,hao to do,mail me 296955517@qq.com

Need a receipe to add the mobile template support into a desktop mvc4 project. I am developing a mvc3 multilanguage desktop and mobile app. Right now, I am having to do all this manually.

If you do both better themeing and razor helper support, it would be really good if we could define a razor helper on a default and theme basis

I would like to see a localized device switcher which enables developers to quickly provide the ability for end-users to switch from Index.Mobile.cshtml to Index.Mobile.es-CL.cshtml, or, from Index.cshtml to Index.Mobile.es-CL.cshtml.
Also, I would like the ability to localize a sub-set of views, while allowing other views to “fall back” to a default culture.

I am new to asp.mvc and decided to do my next project on asp.net mvc3. So I am to think about whether I can do everything with mvc that I could do with regular webform. So while I were searching on Google on "how to work with Crystal Report on asp.net mvc3/mvc?", I was dishearten to know that ASP.Net MVC doesn't work well with Crystal Report. But this is very important for developing enterprise application. So I hope that Microsoft will be aware of this issue on their asp.net mvc4 release.

I strongly recommend including a set of "MVC + jQuery" Controls which can be easily used in a MVC Application, something similar to http://www.infragistics.com/dotnet/netadvantage/jquery-controlsoverview.aspx

I would like to see something like Knapsack built-in. Having the ability to combine and compress all javascript (and possibly css) files in release builds would be fantastic. Sure, it's easy enough to add as an extension, but i think this should be part of MVC. This would allow, for instance, the ability for Validators to (optionally) inject their own adapters into the script stream, instead of requiring seperate javascript files.

I would like to suggest changing controller's RedirectToAction method access modifier from protected internal to public.
Because then we could use lambda expressions to eliminate string names of methods when redirecting in controller.
It is described in this article by Patrick Steele for Castle MonoRail:
http://visualstudiomagazine.com/Articles/2011/04/01/pccsp_Expression-Trees.aspx?Page=2

For now I have put extension code into base controller but I think it would be better to put it into extension method.

Please consider adding a site verifier which runs a compiler against all the cshtml files in a project to make sure that when they get published to the server that the necessary assembiles and references are included correctly. Drives me nuts to publish a project to Azure only to find that an assembly wasn't included correctly.

Like @machadogj I would LOVE to see .LESS built-in - why the W3C isn't planning on incorporating LESS into the CSS3 spec I'll never know!

Well, why do not u implement a way to set the deafult language validators? is lacking!

Making it easier to build a site with dynamically generated and compiled views, models, etc. would be great for some apps. But that is a more complex problem.

Better internationalization support. Something less cumbersome than the current explicit resource file model. Phill Haack had an interesting post about "Model Metadata and Validation Localization using Conventions". Something like that (Conventions based) but for strings in the View markup. For example keyed by the View name and id of the html element. Complete with a few simple but convenient hooks in the IDE.
Fix internationalization bugs in client-side validators.

One of the nicest things that could be done to improve ajax functionality would be an easy way to have razor views be used client side as well. Spark has something like this already. I.e. http://odetocode.com/blogs/scott/archive/2009/03/12/client-rendering-views-with-spark-and-asp-net-mvc.aspx

Integration with FluentValidation would be awesome. Attribute-based doesn't cut it for complex scenarios (which validation usually is, in non demoware, by definition...).

+1000 to psBrian re: interfaces for HttpContext et al.

Don't make us write extra code (features or tests) to get around the shortcomings of the ASP.NET framework that we're still sitting on top of, basically.

Take validation completely out of the runtime. I've frequently had requests to let the user define which fields are mandatory, what the error message might be, etc. I'm talking at runtime, the administrative users want to be able to make a decision like "Last name is required, but not first name" and change it in a configuration file, not calling a developer to recompile and deploy the application. Some If/And/Or logic for validation that would emit to the client side would be cool too, such as "either first and last name are required, or LawFirm name is required".

Please update the support for generating more compliant HTML5 markup from the built-in HtmlHelper extensions. For example, HTML5 (as opposed to XHTML5) allows for value-less attributes. I think they are called "boolean attributes". Instead of saying, 'readonly="true"', or 'readonly="readonly"', you should be able to just say "readonly" (without a value). There isn't currently a way to do this without custom HtmlHelper extensions. In summary, I'm sure there is better compliance with the HTML5 spec that can be done with ASP.NET MVC 4. Thanks!

I love the improved mobile support. Why not make the detection/redirection implementation more generic. Meaning if I wanted to redirect mobile views by calling something like: ViewEngines.Engines.Add(new RazorViewEngine(c => c.IsMobileDevice(), "Mobile"); which would do the SomeView.Mobile.cshtml thing. This allows me (the developer) to control the how and where my view redirection is done. So, for example, if I wanted to redirect to a spanish version of a view I could do this: ViewEngines.Engines.Add(new RazorViewEngine(c => c.IsSpanish(), "es"); where I have some custom detection code and would redirect the view to SomeView.es.csthtml

=1 on things already said in comments, KnockOut, CoffeScript, Spriting, improve multiple forms, FluentValidation, PGR

+1 on the idea of Microsoft offering bounties for the recipes / similar development efforts

I hope this feature on MVC 4 even MVC3. Helper or plugin for the File Attach and upload and download. Easily custom ui and events and helpers to handle stream things with the recipe api...

Better validation story. Validation and using attributes is just not flexible enough. For example, validation of a date text box, where the maximum date allowed is today is a big pain. Only static validation things really work. Maybe an integration or direct support of http://fluentvalidation.codeplex.com/ or implement your own....what you have is great for very simple 'demo apps', but anything real is lacking.

Hi just a request if possible. In our current project we are using MVC3. Our application should get data from server the fastest as possible, nearly real time speed. Our data from server is multi-dimensional array instead of JSON key pair values which since json object is quite large. For example in json object of products var products={[['Name':'Product 1', Id:1234], ['Name':'Product2', Id:2345]]}. That somehow heavy so we are using javascript array to become var products={[['Product 1', 1234], ['Product2', 2345]]}. We are using then json template to read the array. Is it possible for to to support javascript array of data which is using indices instead of a key-pair object?

Make the antiforgery token be submitted by default for every form submitted.

Could we please, please, please have a way of turning off the generated ids for html inputs / form field that are always created from the html form helpers? Ids are not a required attribute for those elements and setting a unique HtmlTemplatePrefix to ensure that ids are always unique can be tedious at times.

@haacked - thank you for your reply. And I'm smiling now that I know that you aren't dedicating as much resources to recipies as I initially thought.

I COMPLETELY agree with @psBrian...in our enterprise application the code coverage in the *.web (mvc stack) portion of our solution we have coverage at about 30%, whereas the rest of the solution hovers around 80%. Testing web (not ui) controllers, etc is not straightforward and is a major pain. Please make this easier for us.

Please Read: --> A big pain point in our single page js app is validation code both in the client and server side...and by validation I mean complex business rules that don't fit in a simple annotation. A way to integrate js validation on the server side with the new node.js project would be fantastico!

Please, consider to support localization like http://haacked.com/archive/2011/07/14/model-metadata-and-validation-localization-using-conventions.aspx.
Really please, work out similar and mature support for globalization as well.
Please, natively implement something clean like Rails3 Respond_With – so far, such clean features are big advantage for Rails, the beginning is http://kazimanzurrashid.com/posts/adding-rails-like-actioncontroller-and-respondwith-in-asp-dot-net-mvc-with-restful-way
Then, using MVC4 gives enormous advantage.

may be more SVG for Razor...

Can Controllers please start using an interface for HttpContext so I can design my unit tests without relying on barbaric mocking hacks? Overriding HttpContextBase (and all of its sealed dependencies is a real PITA!)

+1000 for more mobile (i.e. multiple types of client device) support
+100 'official' KO, backbone support

How about a recipe for adding a REST API to your application automagically??? take a look at the django piston framework, it's pretty amazing see https://bitbucket.org/jespern/django-piston/wiki/Home

@Chanva, @sam_dlg *WE* are not planning to implement every recipe. We're working with other teams and hope to have a set of those available via NuGet by the time we launch. We can't possibly write all of those. For example, we're partnering with the P&P team to write some.

Formal strong typed routing would be good. Also a context menu option to build views would be good. Looking very much forward to js/css compilation and recipes.

Out-of-the-box support for the following items:

- Built-in support for the PRG pattern, through controller action filters ?!, along the the following line: http://weblogs.asp.net/rashid/archive/2009/04/01/asp-net-mvc-best-practices-part-1.aspx#prg
- Better support for multiple forms, strongly typed View Data Models, and their client and server side validation and default binding. [Bind(Exclude="...")] is not working properly for such scenarios. What is basically missing is the support for validation groups like in ASP.NET Forms.

+1 for better globalization support.
But I'm sure you guys already had that one the "things to improve" list. Right?

Please consider providing .less files support. Or at least a good way to integrate dotLess.

Before implementing Recipes, I would like to see full globalization/localization support at both server and client(jQuery)!
There is much to improve in the core of MVC.

I like mobile device switching and device specific views! ALso glad to hear you are using the new features of TPL!

CSS and JavaScript bundling would be great together with simpler deployment.
As stated in a comment above, a focus on globalization is crucial for non-english website development. So please make some efforts in this area, in addition to the just mentioned (ModelBinders, Validation on server and client), I'd like to see support for localizing routes (eg. Products/Categories = Produkte/Kategorien = Produits/Categories = ...)

I'd love to see the work done on Templating in v2 taken further. Templating is great for repetative CRUD in e.g. admin modules, and saves a lot of time (money). But in my opinion it's not quite 'there' yet.

How about some first class support for CSS sprites? All the current "best web platforms for building modern rich web apps" natively support these for quite some time now. I would also love to see the adoption of CoffeeScript as well.

There are a few features i'd like to see added to asp.net, the first is multi-tenancy support. Adding multi-tenancy to an MVC app is a huge pain in the rear, and it would be nice to see some kind of hooks to make this simpler.

I agree with the comment above. For single-page apps, please consider embracing Backbone.js like you did with jQuery. Backbone has a large community around it and is a well proven client-side framework for single-page apps.

Why should you implement OAuth-based by yourself? I think that joining the existing Open Source project is better.

and as for one-page js applications please consider both KO & backbone.js first class citizens when building/testing/blogging

improved mvc & javascript collaboration would be nice. A better CSS story would be nice as well.

Though I can appreciate the intent of "recipies" I strongly feel that much more could be done in other areas of MVC. Because quite frankly who ever launches a site with "out of the box" Microsoft code generation? I would rather MS create a "bounty" for NuGet recipies to get these created...please spend your time on the CORE of MVC....there are several posts on how to make it better...just do a little googling...or binging. :-)

Thanks for your contributions.

I would like to see particular focus on making sure globalisation is fully nailed - Model Binders, validation ( componentmodel attributes and jquery validation ). Please test in something other than en-* cultures ;)

How about adding the MvcBuildViews flag to the visual studio tooling, context menu or project properties. Also, fixing the build failures after publishing with MvcBuildViews enabled (due to the transformed web.config in the obj folder).
Looks good though, can't wait for the new async controllers!