Getting Started With ASP.NET MVC - Part One

Introduction

This article explains the basics of ASP.NET MVC and explains the main advantages, version history, and environment setup and folder structures. Here, we can learn how to start first ASP.NET MVC application.

• Getting Started With ASP.NET MVC - Part Two
• Getting Started With ASP.NET MVC - Part Three
• Getting Started With ASP.NET MVC - Part Four

What is ASP.NET MVC

MVC is an architectural pattern. It separates the application into three main components. The three compounds are Model, View, and Controller. It handles specific development aspects of an application. MVC is the most frequently used industry-standard web development framework.

Model

Model is a simple class. It is the shape of the data. The model contains business logic. Controller and View can access the model. The model helps to pass the data from the controller to view and view to the controller. Using the model we are displaying data in the view page.

View

The view is a user interface. It is used to display the entire data using the model. We are using two type of view engines in view. One is the traditional view engine and another one is the Razor view engine. Traditional view engine is normal “.ASPX” page.

Razor view engine is used to develop a normal page design using HTML Helper controls. It contains “.CSHTML” extension. A syntax-wise little bit different in both view engines.

Controller

The controller is the heart of MVC and it handles the user request. It is a simple class. The controller can access the model and pass data to view with the help of a model. We can pass the data between the controller and view using View Data, Temp Data, and View Bag. The controller is intermediate between model and view.

Model-View-Controller

Basic Work Flow of MVC

MVC workflow starts with the user’s request. Based on the request, first, it goes the controller then goes to the corresponding action method. In the action method, we are calling all layers like business logic layer and data access layer.

Once we reach action method then it goes to the Data access layer. Sometimes while requesting, the request contains some input data that binds with the model, then goes to the data access layer.

Request reaches data access layer then goes to the corresponding database. It fetches the data from a database based on the request then goes back to the reverse format. After fetching data and binding in the model it goes to the action method.

Action method returns the result to the corresponding view with the help of model . Now, the user gets the response. Action method returns results in a different format.

Advantages of MVC

• Separation Of Concern (SOC) is the main advantage. Here we are separating Mode, View, and Controller.
• We can easily maintain MVC application.
• Test Drive Development (TDD) is another main advantage. We can create an application with a unit
• We can write our own test case.
• Split the application and many developers can work at a time without affecting each other.
• MVC application is a default responsive web site and mobile template.
• We can create our own view engine.

Is MVC Replacing ASP.NET Web Forms?