Hi
I'm new to single page application development and I see everywhere developers that work on single page application in .NET Framework use ASP.NET MVC, why they use MVC and why they not use Web Forms for single page applications?
thanks
Loading
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
Francis SusaimichaelPosted Aug 10, 2016, 10:22 AM
This is a matter of preference. That's all! There is no rule that prevent you to go with webforms. Comparing to webforms, MVC is "light" weight in the sense, there is no complex "page" life cycle etc. Apart from that, MVC provide more control to render the HTML. These are the some reasons, that I find personally if I go with MVC and SPA. Hope this helps!
Bikesh SrivastavaPosted Aug 10, 2016, 6:52 AM
- Traditional (non-SPA) web apps tend to refresh the entire page when a user submits critical new data (e.g. type of request) or requests (e.g. submit form). Examples of this include apps built using JSPs.
- Forces most of the data validation activity to occur on the server.
- The determination that the submission of page X with data Y should result in the user being taken to page Z is made using the model-view-controller (MVC) architecture, which is implemented on the server
- With the advent of AJAX, web apps started to refresh only the relevant portion of the page when a user submits new data or requests. For example, if a user selects state = Massachusetts, then the web app can immediately use an AJAX request to validate whether the entered zip code is valid for the state of MA. However, once the user submits a form typically the web app takes the user to a new HTML page.
- Some or most of the data validation activity can occur on the client
- The MVC implementation is on the server
- Finally, an SPA moves much of the MVC implementation to the client (using templating frameworks like Mustache and/or MVC frameworks like Backbone, Ember or Angular). Therefore, the new "page" is now virtual and simply involves the determination of the right set of widgets and data to represent to the new state of the page, but doesn't require an actual new HTML page. Therefore, it is called a Single Page Application.
- Much of the data validation activity can occur on the client
- The MVC implementation is on the client
"Vinay SinghPosted Aug 10, 2016, 6:51 AM