Create view models and mappers that cover the initial use cases Album, MediaType, Artist entity view models The following use cases will need view models so go ahead and write them ( AlbumBaseViewModel, MediaTypeBaseViewModel, and ArtistBaseViewModel ) None of these Base classes will have navigatio...

Here are the view model classes and mappers based on the given requirements Album view models public class AlbumBaseViewModel public int AlbumId get s ...

Create view models and mappers that cover the initial use cases Album, MediaType, Artist entity view models

Fantastic news! We've Found the answer you've been seeking!

Question:

Create view models and mappers that cover the initial use cases Album, MediaType, Artist entity view models

The following use cases will need view models so go ahead and write them (AlbumBaseViewModel,
MediaTypeBaseViewModel, and ArtistBaseViewModel). None of these "...Base" classes will have navigation properties
and none of these will have composed (AutoMapper flattened) properties. Keep them simple.
- Artist - "get all"
- Album - "get all"
- MediaType - "get all"

Track entity view model classes

For the track entity, we will support the following use cases:
- Track - "get all"
- Track - "get one"
The TrackBaseViewModel class needs many of the track entity's properties but not all
of them - for example, you can ignore the navigation properties and the MediaTypeId
and GenreId properties.
You will also add a TrackWithDetailViewModel class. It will have a navigation property
to MediaTypeBaseViewModel. It will also have string properties (AutoMapper
flattened) for the associated album and artist descriptive data.
Later, we will need two view model classes, TrackAddFormViewModel and
TrackAddViewModel, to support the use case:
- Track - "add new"

Playlist entity view model classes

In this assignment, you will enable basic editing of a playlist. The following image is an example of what you may end up with after you have completed the assignment.
In the image, you will see two lists of tracks. The list on the left shows all tracks, whether on the playlist or not, and includes the track name, composer, track time/length, and unit price. The list on the right shows a list of existing tracks, including the track name and unit price. The user can use the checkboxes to edit the contents of the playlist.
To render this view, you will need a select list object and a collection:
- The select list will be used to render the checkboxes
- The collection will hold the track objects within the playlist
You will need a PlaylistBaseViewModel class for displaying the playlist. The "edit existing" task will need another two view model classes:
- 1. A view model class named PlaylistEditTracksFormViewModel to hold the data that is needed to render the HTML Form.
- 2. A view model class named PlaylistEditTracksViewModel holds the data submitted by the user.
As noted earlier, the "...Form" view model class will need a select list property (for multiple selections). It will also need another property to hold the collection of tracks that are on the current playlist. Do not forget to include the identifier in this view model class as well as the text (for display purposes).