As i know, You should go with MVC....because this is a new technology and it helps to learn lots of new stuff as well....performance wise also it's good, and there are other lots of features... you can google for that.
Thank you for your reply, but most of these links describe the differences between webforms and MVC. I know there are some differences between these technologies. But as a beginner wantting to learn ASP.NET for jobs, which one do I have to learn? Is WebForm
technology old and there is no job for this technology? Do we have to learn Webforms before starting MVC? the samething for WebPages.
I really appreciate your help. I want to focus on one of them!
As i know, You should go with MVC....because this is a new technology and it helps to learn lots of new stuff as well....performance wise also it's good, and there are other lots of features... you can google for that.
Thanks
Subhash
Thank you for your response.
So before MVC don't I need to learn WebForms? Webfroms technology is not the prerequisite for MVC? I need to mention that I'm a new learner of ASP.NET.
I want to start learning ASP.NET. Among different technologies(WebPage, WebForms,MVC) Which one do you recommend learning?
I prefer to anylasis these concepts other than tell you which is recommended. Which one you decide to learn, you may get idea after reading below(This is my reply for this
thread, it's also useful to you) :
When you create web application, in general there are two kind of framework you can try: ASP.NET web application(using web form), ASP.NET MVC application. For the asp.net web pages, it's also a framework that you can use to create dynamic web pages. It's
dependent which is the best approach to create web application.
When create ASP.NET Web Pages, the development tool is webmatrix which integrates development, testing and publishing, namely it's streamline for developers, that means you can use webmatrix to streamline the way you code, test and publih for your asp.net.
It's amzaing and make all very easy.
For Web Form and ASP.NET MVC application, we use Visual Studio to create them.
In general Web form which is the ASP.NET Web applicaiton developers always use, drag-and-drop and event-driven are its standout point.
ASP.NET MVC is a standard design pattern which helps you create applications that separate the different aspects of the application (input logic, business logic, and UI logic), while providing a loose coupling between these elements. The pattern specifies
where each kind of logic should be located in the application. The UI logic belongs in the view. Input logic belongs in the controller. Business logic belongs in the model.
From above, we can know when you use web form, you may need to create your own BL and entity, web form is a little like the view of mvc.
Now I find some deteailed comparsions about web-form based application and mvc-based applicaiton:
the MVC pattern makes it easier to test applications than it is to test a Web Forms-based ASP.NET Web application. For example, in a Web Forms-based ASP.NET Web application, a single class is used both to display output and to respond to user input. Writing
automated tests for Web Forms-based ASP.NET applications can be complex, because to test an individual page, you must instantiate the page class, all its child controls, and additional dependent classes in the application. Because so many classes are instantiated
to run the page, it can be hard to write tests that focus exclusively on individual parts of the application. Tests for Web Forms-based ASP.NET applications can therefore be more difficult to implement than tests in an MVC application. Moreover, tests in a
Web Forms-based ASP.NET application require a Web server. The MVC framework decouples the components and makes heavy use of interfaces, which makes it possible to test individual components in isolation from the rest of the framework.
Advantages of an MVC-Based Web Application
The ASP.NET MVC framework offers the following advantages:
It makes it easier to manage complexity by dividing an application into the model, the view, and the controller.
It does not use view state or server-based forms. This makes the MVC framework ideal for developers who want full control over the behavior of an application.
It uses a Front Controller pattern that processes Web application requests through a single controller. This enables you to design an application that supports a rich routing infrastructure. For more information, seeFront Controller on the
MSDN Web site.
It provides better support for test-driven development (TDD).
It works well for Web applications that are supported by large teams of developers and Web designers who need a high degree of control over the application behavior.
Advantages of a Web Forms-Based Web Application
The Web Forms-based framework offers the following advantages:
It supports an event model that preserves state over HTTP, which benefits line-of-business Web application development. The Web Forms-based application provides dozens of events that are supported in hundreds of server controls.
It uses a Page Controller pattern that adds functionality to individual pages. For more information, seePage Controller on the MSDN Web site.
It uses view state or server-based forms, which can make managing state information easier.
It works well for small teams of Web developers and designers who want to take advantage of the large number of components available for rapid application development.
In general, it is less complex for application development, because the components (thePage class, controls, and so on) are tightly integrated and usually require less code than the MVC model.
Now you must want to know how to select one of them when you develop web application. The web pages, well, as I mentioned previouly, it streamlines the way you code, test and publish web applicaiton. But because it's development tool is webmatrix, some existed
asp.net features you mightn't use during your developing. For Web-Form and MVC, You must consider carefully whether to implement a Web application by using either the ASP.NET MVC framework or the ASP.NET Web Forms model. The MVC framework does not replace
the Web Forms model; you can use either framework for Web applications. (If you have existing Web Forms-based applications, these continue to work exactly as they always have.) Before you decide to use the MVC framework or the Web Forms model for a specific
Web site, weigh the advantages of each approach(mentioned above).
BTW, these 3 frameworks to create web application, there is no unique anwser for which is the best approach, just which is best sutiable for your specific and practical requirement.
Please mark the replies as answers if they help or unmark if not.
Feedback to us
As a beginer you should understand the difference first between these technologies. Webforms, MVC as well as webpages are used in different scenarios. I strogly recommend you to watch this video to get the difference then decide where you would like head
first.
newcoder61
Member
15 Points
70 Posts
WebPage, WebForms or MVC?
Jul 28, 2012 02:25 AM|LINK
Hello
I want to start learning ASP.NET. Among different technologies(WebPage, WebForms,MVC) Which one do you recommend learning?
Thanks
Ramesh Chand...
Star
12922 Points
2672 Posts
Re: WebPage, WebForms or MVC?
Jul 28, 2012 02:26 AM|LINK
go through these links.
http://channel9.msdn.com/Forums/Coffeehouse/Questions-regarding-Web-pages-vs-Web-forms-vs-MVC
http://forums.asp.net/t/1660149.aspx/1
http://codebetter.com/karlseguin/2010/03/11/webforms-vs-mvc-again/
http://blog.mikecouturier.com/2011/03/aspnet-web-forms-versus-net-mvc.html
subhash.shel...
Contributor
2137 Points
487 Posts
Re: WebPage, WebForms or MVC?
Jul 28, 2012 02:34 AM|LINK
Hi,
As i know, You should go with MVC....because this is a new technology and it helps to learn lots of new stuff as well....performance wise also it's good, and there are other lots of features... you can google for that.
Thanks
Subhash
Subhash
Please, Mark as Answer if this reply helped you.
newcoder61
Member
15 Points
70 Posts
Re: WebPage, WebForms or MVC?
Jul 28, 2012 02:35 AM|LINK
Thank you for your reply, but most of these links describe the differences between webforms and MVC. I know there are some differences between these technologies. But as a beginner wantting to learn ASP.NET for jobs, which one do I have to learn? Is WebForm technology old and there is no job for this technology? Do we have to learn Webforms before starting MVC? the samething for WebPages.
I really appreciate your help. I want to focus on one of them!
Thansk
newcoder61
Member
15 Points
70 Posts
Re: WebPage, WebForms or MVC?
Jul 28, 2012 02:43 AM|LINK
Thank you for your response.
So before MVC don't I need to learn WebForms? Webfroms technology is not the prerequisite for MVC? I need to mention that I'm a new learner of ASP.NET.
Thanks
subhash.shel...
Contributor
2137 Points
487 Posts
Re: WebPage, WebForms or MVC?
Jul 28, 2012 02:46 AM|LINK
Hi,
No...if you new learner then dont need to learn webform etc.....you can direct start with MVC, and how it works etc things...
Best of luck...
Thanks
Subhash
Subhash
Please, Mark as Answer if this reply helped you.
Mamba Dai - ...
All-Star
23531 Points
2683 Posts
Microsoft
Re: WebPage, WebForms or MVC?
Aug 03, 2012 08:23 AM|LINK
Hi,
I prefer to anylasis these concepts other than tell you which is recommended. Which one you decide to learn, you may get idea after reading below(This is my reply for this thread, it's also useful to you) :
When you create web application, in general there are two kind of framework you can try: ASP.NET web application(using web form), ASP.NET MVC application. For the asp.net web pages, it's also a framework that you can use to create dynamic web pages. It's dependent which is the best approach to create web application.
When create ASP.NET Web Pages, the development tool is webmatrix which integrates development, testing and publishing, namely it's streamline for developers, that means you can use webmatrix to streamline the way you code, test and publih for your asp.net. It's amzaing and make all very easy.
For Web Form and ASP.NET MVC application, we use Visual Studio to create them.
In general Web form which is the ASP.NET Web applicaiton developers always use, drag-and-drop and event-driven are its standout point.
ASP.NET MVC is a standard design pattern which helps you create applications that separate the different aspects of the application (input logic, business logic, and UI logic), while providing a loose coupling between these elements. The pattern specifies where each kind of logic should be located in the application. The UI logic belongs in the view. Input logic belongs in the controller. Business logic belongs in the model.
From above, we can know when you use web form, you may need to create your own BL and entity, web form is a little like the view of mvc.
Now I find some deteailed comparsions about web-form based application and mvc-based applicaiton:
the MVC pattern makes it easier to test applications than it is to test a Web Forms-based ASP.NET Web application. For example, in a Web Forms-based ASP.NET Web application, a single class is used both to display output and to respond to user input. Writing automated tests for Web Forms-based ASP.NET applications can be complex, because to test an individual page, you must instantiate the page class, all its child controls, and additional dependent classes in the application. Because so many classes are instantiated to run the page, it can be hard to write tests that focus exclusively on individual parts of the application. Tests for Web Forms-based ASP.NET applications can therefore be more difficult to implement than tests in an MVC application. Moreover, tests in a Web Forms-based ASP.NET application require a Web server. The MVC framework decouples the components and makes heavy use of interfaces, which makes it possible to test individual components in isolation from the rest of the framework.
Advantages of an MVC-Based Web Application
The ASP.NET MVC framework offers the following advantages:
Advantages of a Web Forms-Based Web Application
The Web Forms-based framework offers the following advantages:
Now you must want to know how to select one of them when you develop web application. The web pages, well, as I mentioned previouly, it streamlines the way you code, test and publish web applicaiton. But because it's development tool is webmatrix, some existed asp.net features you mightn't use during your developing. For Web-Form and MVC, You must consider carefully whether to implement a Web application by using either the ASP.NET MVC framework or the ASP.NET Web Forms model. The MVC framework does not replace the Web Forms model; you can use either framework for Web applications. (If you have existing Web Forms-based applications, these continue to work exactly as they always have.) Before you decide to use the MVC framework or the Web Forms model for a specific Web site, weigh the advantages of each approach(mentioned above).
BTW, these 3 frameworks to create web application, there is no unique anwser for which is the best approach, just which is best sutiable for your specific and practical requirement.
Feedback to us
Develop and promote your apps in Windows Store
GaurangNaik
Contributor
2080 Points
498 Posts
Re: WebPage, WebForms or MVC?
Aug 03, 2012 08:28 AM|LINK
Hi,
As a beginer you should understand the difference first between these technologies. Webforms, MVC as well as webpages are used in different scenarios. I strogly recommend you to watch this video to get the difference then decide where you would like head first.
http://www.asp.net/web-forms/videos/how-do-i/choosing-the-right-programming-model
Its always best to know all rather than just one.
GauranG