Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m currently working with ASP.NET and about to start learning ASP.NET MVC (2).
So before I open the first thick book and go through the first lengthy tutorial, what are the most important (new) concepts to keep in mind? What are the main new features I should be aware of?
Thanks a lot.
No viewstate. No server-side controls. Think RESTful/stateless; it’s a request/response cycle, not an event being handled.
It’s worth consideration to take a side trip into Ruby/Rails to learn the concepts completely outside the .NET stack before you tackle MVC. I know that I was able to pick it up pretty quickly because I had already dabbled in Ruby/Rails enough to be familiar with the paradigm.
EDIT: I would also add that I find that separating view models from business models (entities) is a good idea. You should definitely be using strongly-typed views and passing models around rather than passing “untyped” ViewData to your views and pulling “untyped” data from the request or value providers directly. Using models and making the model-binding framework work for you will make it much easier both to test and keep your views cleaner. Using strongly-typed data in your views will at least give you some compile-time checking there as well.