The .NET MVC Framework – Part 4 – Conclusions and Code
Over the past few days, I’ve written about what the MVC framework is and provided a prototype example using the existing photo gallery for this blog.
Download the Project Code: Here
Is the MVC Framework a replacement for web forms?
No. I don’t think so and haven’t seen any evidence from Microsoft to indicate such. I think it’s setup to be an alternative—just as it is with frameworks like Java. Right off the top, for things even like the photo gallery example, I can see this being overkill. On the other side of the coin, I can think of a few applications I’ve rolled out in the past year that emulated MVC to a degree (as far as separation), but were somewhat of a pain to test—and would greatly benefit from this framework.
Is the MVC Framework easier?
Ehh, honestly? No, but you end up getting more in the end for your work. Properly implemented, your output code is slimmer (lacking ViewState data, etc), cleaner, and you have gained full testability of your code. The theory is that you could take the Controllers and Models, drop them into another environment (or another UI) and they’d work—no fuss needed. Unfortunately, since MVC is web-only right now, I don’t have a good way to test that right now.
For now, the best bet is familiarization—seeing how each of these new technologies work, their pros and cons, and using that knowledge to make better design decisions down the road.