[eckyptang]

Not for a minute. The releases are pretty much shelved after v.next. To add to that, the support you do get is crappy, even as a gold partner. ASP.Net MVC is awfully designed and rather buggy as well from experience.

I've been using it on a huge project (145 controllers)since CTP2. I wouldn't use it again.

we're currently investigating werkzeug, python, sqlalchemy and postgresql as a replacement for a new project, particularly also because we got shafted by SQL 2012 per core licensing.

Stay away - you have been warned.

[DennisP]

I've built a fair number of medium-small sites with it and like it pretty well...I'm interested in your perspective with such a large project. Why do you think it's awfully designed?

I did just run into a pretty nasty and obscure bug. (That was the first though.)

[jongalloway2]

What was the bug? I'd like to make sure it's listed on https://aspnetwebstack.codeplex.com/workitem/list/basic if it's not there already.

[DennisP]

This one: http://stackoverflow.com/questions/8640950/null-reference-ex...

In my case it manifested on ajax calls but not the initial page load. I had a custom grid that worked fine on the first load but blew up when the user tried to page or sort it. And it only happened on production, because the prod server had the component mentioned in the link installed, but the dev and stage servers didn't.

Luckily the guy administering the web servers tracked down the configuration difference, googled, and found the above link, and I was able to make a small change to my code to work around it, pre-calculating the url on the initial load and just referencing the resulting string on the ajax call (specifically, using lexical closure instead of calculating the url inside a lambda). That fixed it.

This was on MVC3.