Lately, I’ve been having a lot of conversations about ASP.NET MVC. I’ve been following this technology for quite some time and delivered a couple of technical sessions around it that were very appreciated by the audiences.
Unfortunately, usually being limited to one hour talks, I don’t have enough time to fully explore the ins and outs of the technology, although I do try my best to deliver content that has some depth to it.
It came to my attention through the extensive feedback I’ve been receiving, that there are some common misconceptions about this subject that should be clarified. So, in this series of posts around ASP.NET MVC, I’ll do my best to cover some of the frequent questions I see.
Let’s start with the most basic one which usually is followed by other more interesting questions:
Q: “Can I use ASP.NET MVC to <insert random thing that you do with ASP.NET Web Forms>?”
A: Yes, you sure can. The framework is different but not limitative in any way.
The mindset is different; you have to lose the notion of pages, events and controls that have been the foundation of your work so far, if you have been developing web applications on ASP.NET Web Forms.
However, once you get round to it, you will surely have fun with it, even if you feel you are less productive. To a certain extent, this is also a question of establishing the correct mindset and not so much actual truth. Just because we got used to dragging controls to a page, quickly bind whatever data we want and get tons of rich functionality prepared for us, that doesn’t mean this is the ONLY way of achieving our goals quickly and efficiently. Some people seem to find all this “out-of-the-box” behavior a bit inconvenient, and spend quite a lot of time struggling against it.
Anyway, ASP.NET MVC is not for everyone, and I don’t mean to make it sound elitist in anyway. While MVC will please the developers that were unhappy with the lesser degree of control they had in Web Forms applications, it will surely make other developers feel like they are being taken a few steps back in evolution.
ASP.NET MVC is an alternative to Web Forms, one that is not better or worse. You should take a look at it once you have the chance and decide what fits you best. I made my pick for sure, MVC is much more pleasing to my style of development and I love the experience so far.