Asp.Net MVC...Glorified Property Bag?

Question

Asp Mvc feels like a glorified property bag from the examples I've seen on www.asp.net. My perception of MVC is that the controller can delegate actions that need to be completed by the view and manage the general flow of the system. I'm I perceiving MVC incorrectly? Where can I find better examples of how to use asp.Net MVC?

Edit: This was asked when I was first using ASP.NET MVC (MVC 1.0 was in it's infancy on top of that). Since then ASP.NET MVC has evolved into a very powerful platform. I will never touch WebForms again if I can avoid it ;-).

Answer 1

check out the NerdDinner.com tutorial here

Answer 2

Have you seen this tutorial? It walks you through the creation of the nerd dinners site (http://www.nerddinner.com/). I just barely got started with it last weekend, so I can't say how useful you might find it, but it looks interesting, so far.

Answer 3

I agree that MVC can be used that way, but there's more:

• All posts and gets map to a controller action, not a page. You decide what the view should be. The view translates loosely to WebForm page contents.
• Routing. Fancy urls or not, you decide.
• No postbacks or complex page life cycle issues. Simpler code hopefully creates fewer bugs.
• Follow the conventions suggested in the aforementioned tutorial, and you get cleaner code which adheres to Separation of Concerns. Nice words, but that too should give you more maintainable code.