ASP.NET MVC - Managing large projects
This is more of a design question than a problem I'm trying to solve. I'm posting this here to get other people's opinion on the Design of the ASP.NET MVC framework.

To start with, I'll state the issues I have with the framework:
1. Html and code in views
2. Method names such as View() where one can't discern by looking at the name what it is doing and that it actually returns something
3. Too many overloaded methods that accept completely different parameters (like View())
4. Html Helpers - I don't believe Extension method were introduced for this use
5. ViewData

I'm not explaining in detail the issues I have have with the above in the hopes that there are others who see the problems I see. To be honest, I haven't anyone bring up these issues so I'm beginning to wonder if I'm alone :).

Someone somewhere must see/feel these issues when building large applications no?
ASP.NET MVC - Managing large projects
===

This is more of a design question than a problem I'm trying to solve. I'm posting this here to get other people's opinion on the Design of the ASP.NET MVC framework.

To start with, I'll state the issues I have with the framework:
1. Html and code in views
2. Method names such as View() where one can't discern by looking at the name what it is doing and that it actually returns something
3. Too many overloaded methods that accept completely different parameters (like View())
4. Html Helpers - I don't believe Extension method were introduced for this use
5. ViewData

I'm not explaining in detail the issues I have have with the above in the hopes that there are others who see the problems I see. To be honest, I haven't anyone bring up these issues so I'm beginning to wonder if I'm alone :).

Someone somewhere must see/feel these issues when building large applications no?