Is ASP.NET MVC an erroneous implementation of the MVC architect pattern?

Question

Background: I have been thinking about this for quite some time, and I have not found any good answer to it. After some time working with WebForms and periodically with MVC 2,3 and 4, I still do not understand how ASP.NET MVC can claim to implement the MVC pattern.

One of the first things I learned about MVC (pattern) is that it is cyclic - this means that the view uses a controller that updates the model, which updates the view, and so it goes, rounded and round. Naturally, the user in the circle enters new instructions / data, etc.

However, ASP.NET MVC is not really a looping implementation, which is well demonstrated in the color image below from W3CSchools. I also saw this in practice when the View has an instance of the Model and the Model is updated from the Controller, but where the Controller is also responsible for updating the View after the Model has been updated.

Question: Is ASP.NET MVC mistakenly implemented consciously and should it be considered only as a proprietary interpretation, or have I misunderstood the rules of the MVC pattern?

Answer 1

The Database model does not update the view, the controller updates the view when transmitting the View Model, if you use separate view models (what you need)