ASP.NET MVC Tutorialprovides basic and advanced concepts of C# for beginners and professionals.

  1. Home
  2. ASP.NET MVC Tutorial

ASP.NET MVC Model

Back to: ASP.NET MVC Tutorial

In ASP.NET MVC (Model-View-Controller), the "Model" represents the data and business logic of the application. It acts as the foundation for interacting with data, processing it, and preparing it for the view. Here’s an overview of the ASP.NET MVC Model:

1. Purpose of the Model

  • The Model in ASP.NET MVC is responsible for handling data logic, validation, and interactions with the database.
  • It serves as a bridge between the View and Controller, allowing the Controller to pull data to pass to the View and handle data sent back by the View.

2. Types of Models

  • Domain Models: Represent the entities and business logic of your application, typically in the form of classes.
  • View Models: Custom objects specifically designed to contain data needed by a specific view. They’re often used to combine properties from multiple domain models or to tailor data for the view.
  • Data Transfer Objects (DTOs): Light-weight objects used to transfer data between processes, often used in service layers or Web API projects.

3. Working with Models in ASP.NET MVC

  • Creating Models: Models are classes written in C#. They often include properties that correspond to database fields and additional methods for business logic.
  • Data Annotations: These provide a way to validate models and apply attributes like Required, StringLength, or Range.
  • Database Interaction: In ASP.NET MVC, Entity Framework (EF) is commonly used as an ORM (Object-Relational Mapper) to map models to database tables and handle CRUD operations.

4. Example of a Model in ASP.NET MVC

using System;
using System.ComponentModel.DataAnnotations;
public class Product
{
[Key]
public int Id { get; set; }
[Required] [StringLength(100)]
public string Name { get; set; }
[Range(0, 10000)]
public decimal Price
{ get; set; }
[DataType(DataType.Date)]
public DateTime CreatedDate
{ get; set; }
}

 

5. Binding and Validating Models

  • When forms in a view are submitted, data is bound to the model in the Controller.
  • Model Binding automatically maps form fields to model properties based on name matching.
  • Validation occurs during this process, allowing the application to ensure all required fields are filled correctly.

6. Using Models in Controllers

  • In the Controller, models are typically fetched, modified, and passed to the View.
  • Here’s an example of an action that uses a model:
public class ProductController : Controller
{
private ApplicationDbContext db = new ApplicationDbContext();
public ActionResult Details(int id)
{
var product = db.Products.Find(id);
if (product == null)
{
return HttpNotFound();
}
return View(product);
}
}

 

Benefits of Using Models in ASP.NET MVC

  • Separation of Concerns: By separating data logic (Model) from UI (View) and application flow (Controller), MVC promotes clean and maintainable code.
  • Reusability: Models are reusable and can be used across various parts of the application or in APIs.
  • Testability: Testing becomes easier because Models, Controllers, and Views can be tested in isolation.
Scroll to Top