I am going to start a new project. Before we have used ASP.NET Web Forms (with Ajax support), no we are looking into ASP.NET MVC for this new application. But what the big diffreneces and benefist by changing to ASP.NET MVC?
As far as I can see it has no support for control events, so for example if I have two dropdown list where the second ones content is dependent upon the selection in the first one. How is this resolved?
That ASP.NET MVC support test-driven development, allows you to create user-friendly and search engine–friendly URLs. That not so important if you don't have any easy programming model that support the things we are used to from ASP.NET Web Forms, such as
the event and postback mechanism. How are these things handled in ASP. NET MVC? How do you program these things in ASP.NET MVC?
ASP.NET MVC Web Forms eventsserver controlespostback
ASP.NET MVC and ASP.NET can be based on the following five criteria or more..:
1. Are you considering test-driven development (TDD)? TDD enables you to write tests for an application first, after which the application logic is developed. An ASP.NET Webforms application uses only one class to display output and handle user input. Automated
testing of this class is complex as you are required to load the full ASP.NET stack into a
separate process (for example, in IIS). The MVC framework allows the testing of each component separately, without requiring the full ASP.NET stack. For example, you can test your model separately from your controller without
requiring a view. If you are considering TDD, the ASP.NET MVC framework will be the better choice.
2. Is there a need for fine control over HTML markup? ASP.NET Webforms automatically inserts hidden HTML markup, IDs, JavaScript, and so on, into your page’s HTML output because of its event‑driven architecture and its use of ViewState. The ASP.NET MVC framework
allows for 100% control over the HTML output. If you require full
control over your HTML markup, the ASP.NET MVC framework will be the better choice.
3. Is the application heavily data-driven? If you are developing an application that is heavily data-driven and is using grids or a lot of master-detail editing of data, ASP.NET Webforms may be the better choice as it provides a lot of controls that will
aid you in the development of these kind of applications. Of course, you can use the ASP.NET MVC framework for these tasks too, but you will be required to write more code to achieve the same goal.
4. Is there a need for a Winforms-like development approach? Does your development team write Winforms code? Is there a need for an event-driven programming approach? In these cases, consider ASP.NET
Webforms in favor of ASP.NET MVC.
5. Is there a need for a rapid application development (RAD) development approach?
Does your client expect a quick prototype of an application? Is the use of drag-and-drop development using pre-created web controls required? If so, consider ASP.NET Webforms in favor of ASP.NET MVC.
and you need to watch this 80 minutes video in order to get a good grip
An in-depth tutorial on building an application with ASP.NET MVC. In this video we build the basics of Nerddinner.com and cover issues such as Unit Testing, Javascript (using jQuery), and how to use the new tooling features for Visual Studio 2008 which are
installed with the ASP.NET MVC project templates
kimf
Member
14 Points
18 Posts
What to select Web Forms or MVC
Sep 14, 2009 12:58 PM|LINK
Hi,
I am going to start a new project. Before we have used ASP.NET Web Forms (with Ajax support), no we are looking into ASP.NET MVC for this new application. But what the big diffreneces and benefist by changing to ASP.NET MVC?
As far as I can see it has no support for control events, so for example if I have two dropdown list where the second ones content is dependent upon the selection in the first one. How is this resolved?
That ASP.NET MVC support test-driven development, allows you to create user-friendly and search engine–friendly URLs. That not so important if you don't have any easy programming model that support the things we are used to from ASP.NET Web Forms, such as the event and postback mechanism. How are these things handled in ASP. NET MVC? How do you program these things in ASP.NET MVC?
ASP.NET MVC Web Forms events server controles postback
joaoluizbt
Member
34 Points
80 Posts
Re: What to select Web Forms or MVC
Sep 14, 2009 02:02 PM|LINK
MVC is more worthy to make big programs, you use tree layres (Model, View, Controller).
the view dont see directly the database, it only shows the information tooked by model, and processed by controller.
things like cascading dropdownlist you have to use javascript.
MVC is better to use test units.
Look these links.
http://www.asp.net/mvc
http://stackoverflow.com/questions/416218/what-are-the-main-differences-between-asp-net-mvc-and-fubumvc
http://msdn.microsoft.com/en-us/magazine/dd942833.aspx
joaoluizbt@hotmail.com
joaoluizbt@gmail.com
nisarkhan
Contributor
2402 Points
1472 Posts
Re: What to select Web Forms or MVC
Sep 14, 2009 07:13 PM|LINK
ASP.NET MVC and ASP.NET can be based on the following five criteria or more..:
1. Are you considering test-driven development (TDD)? TDD enables you to write tests for an application first, after which the application logic is developed. An ASP.NET Webforms application uses only one class to display output and handle user input. Automated testing of this class is complex as you are required to load the full ASP.NET stack into a
separate process (for example, in IIS). The MVC framework allows the testing of each component separately, without requiring the full ASP.NET stack. For example, you can test your model separately from your controller without
requiring a view. If you are considering TDD, the ASP.NET MVC framework will be the better choice.
2. Is there a need for fine control over HTML markup? ASP.NET Webforms automatically inserts hidden HTML markup, IDs, JavaScript, and so on, into your page’s HTML output because of its event‑driven architecture and its use of ViewState. The ASP.NET MVC framework allows for 100% control over the HTML output. If you require full
control over your HTML markup, the ASP.NET MVC framework will be the better choice.
3. Is the application heavily data-driven? If you are developing an application that is heavily data-driven and is using grids or a lot of master-detail editing of data, ASP.NET Webforms may be the better choice as it provides a lot of controls that will aid you in the development of these kind of applications. Of course, you can use the ASP.NET MVC framework for these tasks too, but you will be required to write more code to achieve the same goal.
4. Is there a need for a Winforms-like development approach? Does your development team write Winforms code? Is there a need for an event-driven programming approach? In these cases, consider ASP.NET
Webforms in favor of ASP.NET MVC.
5. Is there a need for a rapid application development (RAD) development approach?
Does your client expect a quick prototype of an application? Is the use of drag-and-drop development using pre-created web controls required? If so, consider ASP.NET Webforms in favor of ASP.NET MVC.
and you need to watch this 80 minutes video in order to get a good grip
An in-depth tutorial on building an application with ASP.NET MVC. In this video we build the basics of Nerddinner.com and cover issues such as Unit Testing, Javascript (using jQuery), and how to use the new tooling features for Visual Studio 2008 which are installed with the ASP.NET MVC project templates
http://www.asp.net/learn/mvc-videos/video-8143.aspx
--------------------------
Don't forget to click "Mark as Answer" on the post(s) that helped you.
ricka6
All-Star
15070 Points
2272 Posts
Microsoft
Moderator
Re: What to select Web Forms or MVC
Sep 14, 2009 08:32 PM|LINK
Excellent responses. I would suggest you review the links and build a small proto-type with MVC. Here are a few more links.
article by shiju varghese
and a question on SO
http://www.bing.com/search?q=+MVC+advantages+asp.net&go=&form=QBRE&qs=n