Comments on: MVC vs. WebForms. Stop It.

By: Randall Tomes

Randall Tomes — Fri, 02 Dec 2011 19:24:00 +0000

MVC would be better for this type. Is is a marketing style web site? or complexe application impersonating a thick client online? Do you see reusing many slick custom server controls in the app? Then stick with WebForms. Is this a marketing style website and there is going to be a lot of client script integration with 3rd party wigets. The website will have some forms but mostly is html design? Then mvc works better. Basically, your project more like a website? or a rich thick client that will be available online? MVC is bad when it comes to resuasable controls but great for mulit technology http integration like that is needed in many real world web sites. Once you learn mvc the speed difference becomes about equal. If you are trying to build the next online SAP i wouldn’t recommend doing that with MVC because you are going to want as much code as possible using OOP. MVC is good if you are just posting back some forms and collecting info. This is my humble opinion on it having worked with both now extensively.

By: Amaury C

Amaury C — Thu, 01 Dec 2011 20:19:00 +0000

My questions are…… Which technology will offer better employ-ability for 2012/2013? ASP.NET Webform or ASP.NET MVC?

Which technology should a junior developer pick?

Thanks

By: Coach Factory Outlet

Coach Factory Outlet — Wed, 30 Nov 2011 06:51:00 +0000

http://www.buycoachfactoryoutlet.net Coach Factory Outlet

By: Aa

Aa — Tue, 20 Sep 2011 14:45:00 +0000

aaa

By: JonnyB

JonnyB — Wed, 14 Sep 2011 15:28:00 +0000

Great post and very well said. Thanks for putting this out there. I’m guilty of getting caught up in the need to use the latest and greatest, but MS doesn’t help things. It gets to the point where you feel like you’re being force fed…whether its MVVM, MVC, Agile dev, etc. I 100% agree…use the tools that are right for the job.

By: Reality Bites

Reality Bites — Wed, 31 Aug 2011 16:34:00 +0000

Interesting that almost no one is considering the non-functional characteristics of these solutions like long-term maintainability, scalability, security…

By: Bryan

Bryan — Sat, 25 Jun 2011 21:34:00 +0000

My, my my. I usually don’t respond to the purest rants but I have to on this one. I was one of them but then reality sets in. MVC is NOT superior to Webforms and this developing the wrong way with Winforms is rediculous. MVC leads to the age old problem… separation of duties. Now i have a developer writing javascript and designing layout. Winforms allow large shops to have designers be designers. MVC is good for dipciplined developers otherwise you get a mess. You have code in your business in your models and views that belong in the HTML. Finally, we have large APIs written that host business logic that is used across winforms, webforms and WCF. Winforms is better for rapid binding etc.. MVC is yes aother place for a developer lacking wisdom to preach he is better than he is.

By: reality101

reality101 — Sat, 04 Jun 2011 14:15:00 +0000

The problem I see with asp.net mvc, you loose your shirt because the time it takes to complete anything beyond trivial pages. If you want more than the trivial, you need an expert in Javascript, ajax, css and linq to get anything done. And it still takes that “expert” 3-4 times longer to produce something that I can complete in standard asp.net with a good component provider with better results in a fraction of the time. Are we in the business to waste money or get something done?

And the arguments I see on blogs against asp.net appear to be written by authors who no little about OOP and how it is applied easily to the event model in asp.net to produce powerful frameworks that completely kick but on asp.net mvc…

By: Donn Felker

Donn Felker — Wed, 01 Jun 2011 17:41:00 +0000

Very well said. You can definitely have some garbage mvc apps. I’ve seen
plenty of them.

By: Sciencedev

Sciencedev — Wed, 01 Jun 2011 11:50:00 +0000

separation of concerns, testability are great and can be done in webforms via model view presenter and using other patterns. Yes despite all the marketing points MS is pushing out with MVC you can have a poorly written MVC app and a poorly written Web form app