All language subtitles for 1. What is MVC

Bird definition and stands for model view controller.

But what are these concepts and how are they related to each other?

A model is just a C sharp claws that represents a table in the school server in this case.

So basically serves as a data blueprint and can also be used to define the data relations.

So, for example, in our app, we have producers, we have movies, we have actors, etc. Now to store

all this data in our database, we need to create tables and to create tables.

We are going to create the models.

So, for example, we are going to have producer, model, movie model, actor, etc.

A view is a name already indicates is what the user gets to see.

So it is a file that represents the user interface.

And an MVC view is a C.

S HD Amalfi, where C.

S stands for C Sharp and HD ammo for the HDMI code.

So the C sharp HTML files or the razor views, as we call them, are just a combination of the C sharp

and the HDMI code from The View.

You can trigger the request or the events that get handled by the controllers.

Now, a controller will receive the events, then will prepare a response, and then just return the

response to the view.

A controller is just a C sharp claws that inherits from the controller base class.

Throughout this course, you are going to create producer controller, movie controller, actors, controller,

etc. But how are the views, the models and the controllers related to each other now to better understand

the MVC?

Let us first think as an example, a Web application.

Now, in a Web application, you have a browser, you have the server and a database.

The way these components work with each other is that you sent a request from the browser.

You send it from the browser to the server.

Then the server will gather data from the database.

And once the data is ready, this server will return the data to the browser the same way in MVC.

Now, instead of a browser, you have a view.

Then instead of a server, you have a controller and then instead of the database, you have the models

which are used to communicate with the database.

So let us see the user clicks on a button or just searches for a movie.

In our case, then the request will be sent from the view to the controller.

Then the controller will get the request based on the parameters or no parameters at all.

We'll construct a response by getting some data from the database using models.

And once the response is ready, the response will be returned to The View.

So let us go to the EP that we're going to build.

So when you first seen here is The View song here we have, for example, in our EP, we have a view

that is used to display all the movies.

But if you go to, for example, the show details, this is another view that is used to return data.

So basically, when you are in the movies and then click in here, these show details.

So I'm now sending a request to a controller.

The controller will get the request.

So in this case, is the home controller details action result?

And if Parmeter is the ID number three, it will get some data from the database by using the models,

the necessary models.

And then we turn the response to the view.

So you basically have a controller which will get a request from the view, use the models to get some

data from the database and then return another view, or it can be the same view with some data.