I've been developing with forms for a few years now, and am exploring the advantages of MVC (specifically, I'm trying it out on an in-house CMS that I'm developing)
I know there are many opinions of what the differences are between a web designer and a web developer, but in my organization the main difference is that the designers do the HTML/CSS/Graphics and the developers do the rest. I've been able to keep our designers pretty happy for the last couple of years using forms by basically avoiding all MS Toolkit Controls (except the repeater and the placeholder) and just using code nuggets here and there on the aspx pages.
My initial opinions of MVC are that, as a developer I absolutely love it, but I just know my designers are going to freak out when they see all the foreaches and curly brackets. It'll probably lead to us not being able to use it here. So I'm trying to build up a "for" case at the moment. Has anyone else faced the same problem or does anyone know of any good resources about building a tight framework in MVC where the frontend is designer friendly?
View Complete Post