nice video but i got confused. if you got an instance of member and an instance of rental. do both keep a copy of each other in their respective attribute? how does that work if you need to instantiate them if you need both for the instantiation? (circular)
Thank you sir for your explanations I want to ask one question please, why you put ICollection of Member in Rental class that mean every time the rental data will repeated and the only change will be MemberId ?
Thank you for your videos. They helped me to understand much easier. Please suggest where should the Mapping between Domain Objects and View Objects should be done? Should it be done in Application Layer?
Thanks alot for the feedback. I was planing on adding that later once the movie rental business use case was added in the next video. I wanted to add that with Auditable Entry so that in the future when data is changed we must know by who and also when we introduce user management capability. But should there be an urgent need I can bring it in sooner
@@CodeUnparalleled I mean to say in video( ruclips.net/video/HCuoBwXS95o/видео.html), create repositories and services for models used from this video(ruclips.net/video/KeTi_x8_4ao/видео.html).
Thanks a lot...really learning a lot from your videos..Waiting for next video in series.
Thanks alot . More videos coming
gracias!!!!
Thank you sir!
Thank you sir for your explanations! I never saw how actually work with EF (not counting Identity stuff here).
nice video but i got confused. if you got an instance of member and an instance of rental. do both keep a copy of each other in their respective attribute? how does that work if you need to instantiate them if you need both for the instantiation? (circular)
You would only interact with them using the EF. If you need them in the business logic, then you'll have another DTO data model
Thanks sir
So nice of you
you explain very well sir, thanks for the video +1 subscriber, hope for next videos!
Thanks alot
I think that you have to fix the relation between Member and Rental in code...
I will need to check on thya
The mapping is wrong. one member has many rentals but one rental only belong to one member. seem like you do the opposite side in you c# classes.
Will have to check it out
Thank you sir for your explanations I want to ask one question please, why you put ICollection of Member in Rental class that mean every time the rental data will repeated and the only change will be MemberId ?
Thank you for your videos. They helped me to understand much easier.
Please suggest where should the Mapping between Domain Objects and View Objects should be done?
Should it be done in Application Layer?
Am planning on making a video on that.
So be on the look out
Where to add ASP.NET Core Identity in terms of this Clean solution?
Thanks alot for the feedback. I was planing on adding that later once the movie rental business use case was added in the next video.
I wanted to add that with Auditable Entry so that in the future when data is changed we must know by who and also when we introduce user management capability.
But should there be an urgent need I can bring it in sooner
please create repository/service layer with using these models.
Kindly elaborate
@@CodeUnparalleled I mean to say in video( ruclips.net/video/HCuoBwXS95o/видео.html), create repositories and services for models used from this video(ruclips.net/video/KeTi_x8_4ao/видео.html).
You mean a GitHun Repository?
The video ended on a note that In the Application Layer in the next video We will apply the business logic . That will be covered
@@CodeUnparalleled Ok thanks. Waiting for the next video..