confusion in ViewModel and model in Asp.net MVC

Priyansh Bhaliya

9y1.1k.NET

public class Attendance

{

[Key]
[Column(Order = 1)]
public int GigId { get; set; }

[Key]
[Column(Order = 2)]
public string AttendeeId { get; set; }

public Gigs gig { get; set; }
public ApplicationUser Attendee { get; set; }

}

in above Model: we need GigId and AttendeeId .

we are defined in list

but why create object of same class:

public Gigs gig { get; set; }

public ApplicationUser Attendee { get; set; }

this is ViewModel or Model ???

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Saravanan V9y ago
Accepted answer
First, you need to understand the purpose of ViewModel and Model classes.
The purpose of a ViewModel is for the view to have an object to render data in the Html page.
It helps in achieving the separation of concerns by isolating the domain model information.

Your view should not have to know the details of your domain models.
Your viewmodel( or presentation model) is specific to the view and you should not have the viewmodel referenced in any other layers of project except the presentation/Web layer.

On the other hand, model is typically referred as your application domain model which would be matching the structure of the respective table in the database.

You use the domain models while doing the business validations, CRUD operations etc.

I found below article which also explains the same.

http://www.c-sharpcorner.com/UploadFile/abhikumarvatsa/what-is-model-and-viewmodel-in-mvc-pattern/
Rajkiran Swain9y ago
http://stevemichelotti.com/aspnet-mvc-view-model-patterns/
Priyansh Bhaliya9y ago
but why need this class object in Attendance class
we only need one property from each class

public Gigs gig { get; set; }
public ApplicationUser Attendee { get; set; }
Manikandan Murugesan9y ago
Refer the following link to clear your confusion : https://stackoverflow.com/questions/4061440/asp-net-mvc-model-vs-viewmodel

The above code is Model not viewmodel.