I'm learning about MVC and am wondering if there is more to it other than the concept of view->control->model?
What is ASP.NET's MVC, is it again just the method of splitting front end, processing and data up - as with the general idea of MVC?
+1
A:
MVC is an architectural pattern. I advice you to read the wikipedia definition where the concept of MVC has been easy explained.
ASP.NET MVC is a framwork that implements the MVC pattern on the .NET world.
Lorenzo
2010-10-13 22:58:45
Thanks for pointing me in the direction of architectural patterns. I'll have to give ASP.NET's MVC framework a go before I think I'll fully understand it.
Nathan
2010-10-13 23:17:48
You're welcome Nathan!
Lorenzo
2010-10-13 23:34:20
A:
As Lorenzo said, MVC is a programming model, first described in 1979 by someone working at XEROX (history here). Now... what is to .NET? It allows you to have full control over your markup (clean HTML), implements latest technologies (JASON, REST), enforces newest concepts (DRY, inference, etc)... and testing.
I personally find it very powerful and interesting, in some cases easier and faster to develop websites, and I like the separation of concerns idea. Still yet have to think of standards for coding, like how to separate folders without messing up with the inference stuff, etc.
I specially love the speed (compared to webforms), since now code is cleaner (no more viewstate), mvc websites loads faster, plus now is easier to integrate with jQuery and AJAX to create better interfaces.
If you want more control over the code browser renders and you love working with the metal then .NET MVC is the choice.
Nestor
2010-10-15 03:58:28