Hi Tracy,
Today we'll learn the basics of ASP.NET MVC. So let's get started.
ASP.NET MVC is a framework for building web applications using a MVC (Model View Controller). Let me put each of these in a nutshell.
Today we'll learn the basics of ASP.NET MVC. So let's get started.
ASP.NET MVC is a framework for building web applications using a MVC (Model View Controller). Let me put each of these in a nutshell.
- Model -> Responsible for Handling/using the data required for the application.
- View -> Responsible for presenting the data in the visual format by using the data provided by the model
- Controller -> controls the data retrieval from view to model and provides data from model back to view.
Tracy: Now I understand, but where do I put my business logic in M or V or C?
Good Question! The Business logic are mostly written in the Model layer but there are two types of Buisness Logic.
- Domain Logic
- Application Logic.
Domain logic goes into Model layer. Tracy: That's a no brainer
Where as Application logic is for example rule for logging or tracing or reading only a csv file are not dependent on Domain. We call them as cross cutting concerns. Which can reside in Model or controller or even better a separate layer. (Example like Microsoft Enterprise Libraries).
Tracy: Mr. MVC, Excuse me do I know you?
MVC doesn't want to say Hello World! since, Its been around with us for decades. ASP.NET MVC is a framework built using the MVC architectural pattern.
in the next post let's see what is ASP.NET MVC life Cycle. Where does it starts and what happens after the request hits the IIS.
