ASP.net MVC Vs ASP.net Web Form

re: ASP.net MVC Vs ASP.net Web Form

Mark — Thu, 26 Nov 2009 14:43:58 GMT

Anybody who says you can't build enterprise applications with MVC and should only use it for hello world is not getting it at all and is not adding to the debate at all. I am developing a web application for a large enterprise using MVC with no problems at all.

re: ASP.net MVC Vs ASP.net Web Form

shiju — Sat, 12 Sep 2009 06:01:05 GMT

@Manoj You can possible to use multiple submit buttons. Check this link stackoverflow.com/.../how-do-you-handle-multiple-submit-buttons-in-asp-net-mvc-framework

re: ASP.net MVC Vs ASP.net Web Form

Manoj — Fri, 11 Sep 2009 10:39:37 GMT

I am new to MVC and haven't formed an opinion or take decision on which way is better. With MVC, is it possible to find what caused the Post to occur considering I have multiple submit buttons (each one doing a separate action at the server end) on the form.

re: ASP.net MVC Vs ASP.net Web Form

jason — Wed, 09 Sep 2009 01:35:04 GMT

right

ASP.NET MVC: What is it and should I use it?

Microsoft Support Team's IIS Blog — Thu, 03 Sep 2009 01:18:56 GMT

In March of this year, we released ASP.NET MVC. Since then, many ASP.NET developers have been perplexed

re: ASP.net MVC Vs ASP.net Web Form

Calvin — Thu, 20 Aug 2009 17:38:20 GMT

nice article & comments! nothing is complex once you master it :) but if you see internally how things works - when you talk about asp.net gridview, its a bit ugly code comparing to asp .net mvc. any component/ 3rd party component developers will agree on this. and the SoC is damn good thing in asp. net mvc. and if you worry about writing more code for creating your own controls, you got 3rd party vendors who already developed asp .net mvc grid and other controls. and i am not saying that asp .net mvc is a replacement for asp .net – but its just a better way of doing :)

happy coding!

re: ASP.net MVC Vs ASP.net Web Form

cnua — Sat, 25 Jul 2009 01:15:36 GMT

thanks for taking the time to write this article. I am a professional developer with 11 years of web development experience and with the last hour and half or so of digging into MVP with intent of finding out its usefulness for the kind of work i do day in, day out i have come to the following conclusion

MVP is not a challenger to the productivity of using WebForms so the .net developer can dispel with any such concerns and get on with their jobs. the reason i say this is because MVP for the non .net developer is a solution package for languages like PHP, easing the application building process and sophistication over basic CGI like capabilities

experienced .net web developers will achieve most of the points listed as advantages of MVP with savy WebForm development. i disagree with you that the webform page life cycle is too complex and urge you to master it and enjoy commercial productivity from n-tiered development. those that have spent years using classic asp javascript html etc to build business applications will relish the power of webforms

re: ASP.net MVC Vs ASP.net Web Form

Mario — Wed, 24 Jun 2009 17:42:28 GMT

Anyone thinks they will more than 50% of mvc programmers anytime soon?

re: ASP.net MVC Vs ASP.net Web Form

Jero — Mon, 15 Jun 2009 22:27:53 GMT

I am trying understand MVC but dont end to get it. If presentation is totally separated from the controller how is possible <ol>, <li> tags and others are included in the OrderListExtensions.cs example you provide??? Sorry for the question if it's too obvious, but I am newbie.

re: ASP.net MVC Vs ASP.net Web Form

bhavtosh — Sun, 14 Jun 2009 07:58:02 GMT

informative content. good work