Are ASP.Net Webforms and ASP.Net MVC component-based or action-based?

Question

I come from the JavaEE background, and I study what kind of web frameworks exist in Java and .NET. As for Java, I found this talk Matt Raible .

One of the categories that he makes among the frameworks is that some of them are based on action, and some of them are based on components. The former are stateless persons and are focused on the action that must be performed for each request and report generation, while the latter are states and retain the representation of their server-side web-based components.

As expected, component-based web frameworks usually come with their own components or third-party component libraries (in addition to its own components, JSF has Richfaces, Icefaces, ... and GWT has ExtGWT, SmartGWT, ...) rich interfaces with action-based frameworks, the developer should use the JS or Flex component library, etc.

Since the advantages and disadvantages for each of these categories make sense to me, I would like to know if this categorization is applicable to .Net frameworks. As far as I managed to find, both ASP.Net MVC and ASP.Net Webforms are idle, but Webforms has a mechanism called Viewstate that can be configured to save and retrieve state from hidden fields, session, etc. However, I could find no representation of the components on the server side.

So, ASP.Net MVC and ASP.Net Webforms based on components or based on actions?

Answer 1

According to your description, it seems to me that Webforms will be based on components, and MVC will be based on action.

Webforms tried to bridge the gap between desktop programming and web programming by providing a way to preserve state in different actions and use the planned programming model.

While MVC is more of a platform for web developers instead of desktop programmers, where you will focus on REST actions and verbs and directly on JavaScript.

Hope this helps!

Answer 2

MVC is definitely based on Action.

Webforms is a component (Control).