Intermediate ASP.NET Core Tutorial - Online Shop Ep.6 - View Models

preview_player
Показать описание
In this episode I show and talk about how to and benefits of keeping your View Models inside your application level and not in your UI layer.

This is more of a break from the last couple of long episodes, so brace your self for some long episodes!

  1. Raw Coding
  2. online shop
  3. shop
  4. making a shop
  5. making online shop
  6. how to make a shop
Рекомендации по теме
ASP.NET Core Tutorial 2:30:14

ASP.NET Core Tutorial – Beginner to Advanced Projects

ASP.NET Core Crash 1:00:44

ASP.NET Core Crash Course - C# App in One Hour

Introduction to ASP.NET 9:26:04

Introduction to ASP.NET Core MVC (.NET 8)

ASP.NET Core Full 3:43:18

ASP.NET Core Full Course For Beginners

ASP.NET Core MVC 2:12:31

ASP.NET Core MVC Course for Beginners (.NET 9)

Full Course - 2:25:32

Full Course - Learn ASP.NET Core MVC in .NET 8 | CRUD Operations | EntityFramework | MVC Tutorial

Intermediate ASP.NET Core 0:04:32

Intermediate ASP.NET Core Tutorial - Online Shop Ep.1 - Introduction

Learn ASP.NET Core 3:07:28

Learn ASP.NET Core MVC (.NET 6) - Full Course

.NET CORE tutorials 0:59:14

.NET CORE tutorials || Demo - 1 || by Mr. Mohan Reddy On 20-01-2025 @8PM IST

ASP NET Core 0:05:35

ASP NET Core Tutorial

Intermediate ASP.NET Core 0:11:55

Intermediate ASP.NET Core Tutorial - Online Shop Ep.18 - Sessions

Intermediate ASP.NET Core 0:10:14

Intermediate ASP.NET Core Tutorial - Online Shop Ep.14 - Multiple Layouts

Intermediate ASP.NET Core 0:23:31

Intermediate ASP.NET Core Tutorial - Online Shop Ep.16 - Stock Management

Intermediate ASP.NET Core 0:12:10

Intermediate ASP.NET Core Tutorial - Online Shop Ep.7 - Products View Model

Intermediate ASP.NET Core 0:03:57

Intermediate ASP.NET Core Tutorial - Online Shop Ep.6 - View Models

Intermediate ASP.NET Core 0:09:51

Intermediate ASP.NET Core Tutorial - Online Shop Ep.5 - Adding Products

Intermediate ASP.NET Core 0:09:31

Intermediate ASP.NET Core Tutorial - Online Shop Ep.3 - Database

Intermediate ASP.NET Core 0:14:35

Intermediate ASP.NET Core Tutorial - Online Shop Ep.26 - Displaying Orders

Intermediate ASP.NET Core 0:11:15

Intermediate ASP.NET Core Tutorial - Online Shop Ep.15 - Stock

Intermediate ASP.NET Core 0:11:01

Intermediate ASP.NET Core Tutorial - Online Shop Ep.4 - Migrations

ASP.NET 9 MVC 4:26:31

ASP.NET 9 MVC Tutorial for Beginners - C# web development made easy #coding #csharp #aspnetcore

Intermediate ASP.NET Core 1:14:05

Intermediate ASP.NET Core Tutorial - Online Shop Ep.39 - Database Extraction

62. .NET Framework 0:25:14

62. .NET Framework vs .NET Core vs .NET vs .NET Standard vs C#

Intermediate ASP.NET Core 0:04:50

Intermediate ASP.NET Core Tutorial - Online Shop Ep.2 - Project Setup

Комментарии
Автор

Most of all, thanks for this excellent series.

I am used to MVVM pattern of Xamarin.Forms.
It seems Ep.5 and Ep.6 shows how to split the concerns of Model, View, and ViewModel by project.

However, the terms of ViewModel in your project looks a little bit different from that of Xamarin MVVM, where VM is handling logics by using models. I think, in your project, each component of Xamarin V-VM-M can be represented by Shop.UI - Shop.Application - Shop.Domain respectively. Shop.Database is providing workers for Shop.Application objects(ViewModel).



My idea is Product property of Index page is just a part of View, not ViewModel. The property just serves as a data basket, to which the model binding of Asp.Net Core hand over data from http request.

The type name of Product property ends with ViewModel and it is very confusing to me.

Normally, ViewModel objects should open methods to View so that View can call on demand. More importantly, parameters of those methods should be in basic types.

A DTO-like objects can be defined to share data between View and ViewModel but i think it is not recommended because ViewModel is a direct child of View so DTO is an unnecessary encapsulation step.

In your project, ProductViewModel is the case. It doesn't only result in more complexity in the name space hierarchy but also produces an extra class that View developers should know to make their View working correctly, while the only thing View maker should know is ViewModel class.

I am not a professional developer and this is not criticizing you. I just look forward to your comments on my idea.

okcharles
Автор

So, basically This is Model-view-viewmodel way of coding and

Shop.Domain is the Model,
Shop.Application is ViewModel,
whereas Shop.UI is the view part right?

Brombrom