Is .NET MVC must learn technology? [closed]

Question

Is it here to stay, or is this something just pushed out quickly as a "me too" offering, in response to the Rails community?

Is it necessary to go through the learning curve, and will the Framework move to only working this way, without the Page behind model?

If so where's the best place to pick up MVC essentials for .NET?

Answer 1

I personally prefer MVC, it's better structured and makes me a happy lad! I got to use MVC for a project at work, because it had to be finished quickly, and I believed that even though I knew no MVC, that I could learn it and finish the project quicker than I could do it using WebForms, and I was right! Learnt MVC and finished the project in a week, with a little help from Stack Overflow!

When I finished it, I had to go back to maintain some WebForms projects, and extend them, I just want to go back to MVC now!

My personal experience.

Answer 2

You won't be forced to use MVC, Webforms are not going away. But it's still a good idea to learn it, because it makes you more marketable; once you've learned MVC on the .Net side, picking up Ruby on Rails or Spring or CakePHP or any one of the other numerous MVC frameworks would be significantly easier.

While Webforms may be easy to learn, MVC is everywhere and for that reason alone it's useful to know.